list_profiles

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

There are no annotations, so the description must carry behavioral disclosure entirely. It correctly implies a read-only listing operation and discloses the supported filtering dimensions (role, tag, enabled), but it does not explain result ordering, pagination, or whether disabled profiles are included by default. This is minimal but not misleading.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, front-loaded with the primary action and followed by the key filtering behavior. The [group: profiles] tag is extra metadata but does not bloat the description; every element earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with no required parameters and no output schema, the description covers the core operation but leaves gaps around expected return shape and exact filter behavior. The sibling get_enum_values could help discover valid values, but the description does not point to it, so the agent must infer some details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description partially compensates by naming all three parameters as filter dimensions (role, tag, enabled). It does not define valid values or matching semantics (exact vs partial), but it at least tells the agent what each parameter is for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb '列出' (list) with a clear resource ('profile') and adds filtering capabilities, making the core action unmistakable. It does not explicitly contrast with sibling tools like get_profile or export_profiles, but the plural 'profiles' and the focused action are enough to differentiate it from single-profile tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to prefer list_profiles over sibling tools such as get_profile, export_profiles, or get_active_profile. The mention of filtering is about parameter usage, not tool selection, so an agent gets no explicit when-to-use or alternatives guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.