list_skills

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

No annotations are provided, so the description carries the full burden. It discloses that the tool lists skills with descriptions and supports filtering, but lacks details on pagination, data format, rate limits, or whether the operation is read-only. For a simple list, this is minimal.

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, front-loaded sentence with no wasted words. It conveys the purpose and optional filtering in a compact form, earning 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 listing tool with one optional parameter and no output schema, the description is largely complete. It could state that the output is a list of objects, but that is implied. It covers the essential information needed for usage.

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?

The input schema only describes 'domain' as 'Optional domain filter.' The description adds significant value by enumerating all valid domain values, which helps the agent correctly select and invoke the filter. Schema coverage is 100%, but description goes beyond.

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 'List USAP skills with one-line descriptions,' specifying the verb, resource, and output format. It distinguishes from sibling tools like 'get_skill' (which likely retrieves a single skill) and 'list_agents' (different resource).

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 explicitly mentions the optional domain filter and lists all valid domain values, providing clear context for usage. However, it does not include guidance on when not to use this tool (e.g., to get a single skill) or mention alternatives like 'get_skill'.

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