list_skills

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, indicating safety. The description adds behavioral detail on how status and tags filters work, which is beyond the annotations. It does not mention pagination or sorting, but given the annotations cover the safety profile, this is acceptable.

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 consists of two clear, concise sentences. The first sentence states the primary purpose, and the second elaborates on filtering behavior. No extraneous information is included, making it efficient and front-loaded.

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?

The description adequately explains core filtering behavior for a list tool but lacks details on the 'limit' and 'source' parameters. There is no output schema, so the agent has no information about the response format. For a tool with 4 parameters and no output schema, the description is somewhat incomplete.

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?

Schema description coverage is only 25% (only status has a description). The description adds meaning for status and tags, explaining their behavior. However, it omits any detail about the 'limit' and 'source' parameters, which remain undocumented. Thus, the description partially compensates for low schema coverage but not completely.

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 clearly states it is a filtered list of skills, mentioning the status and tags filter behavior. It distinguishes its purpose from single-skill retrieval tools like get_skill, though it does not explicitly differentiate from other list tools like list_decisions or list_tags.

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 gives specific guidance on when to use different status values (active vs all vs filtered) and explains that tags use set intersection. However, it does not provide context on when to use this tool versus sibling tools like search_decisions or get_skill, nor does it mention prerequisites or alternatives.

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