List All Skills

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. The description adds valuable context: it reads from manifest (fast, no filesystem scan) and returns formatted output with descriptions. No contradictions.

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 concise: three sentences plus Args/Returns. It front-loads the main purpose, avoids fluff, and is well-structured.

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?

Given no output schema, the description provides a brief return format. Annotations are rich. For a simple list tool with one optional param, it is sufficiently complete, though details like field names are omitted.

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 coverage is 100%. The description says 'filter by category or keyword' but the schema only mentions keyword, causing a slight mismatch. Otherwise, it adds minimal extra beyond the schema's parameter description.

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 'Lists all 484 skills with names and descriptions' specifying verb (lists), resource (skills), and scope (all). It distinguishes from siblings like 'rules_get_skill' by indicating the listing nature and mentions speed advantage.

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 mentions optional filtering by category or keyword, giving clear context for use. It does not explicitly state when to avoid this tool, but given the simple list operation and sibling tools, the usage is well implied.

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