list_skills

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

With no annotations, description discloses that it is cheap to call and returns only name + one-line description, implying no side effects. Could be more explicit about read-only nature, but sufficient for a simple list.

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?

Two sentences, front-loaded with purpose, then usage guidance. No wasted words.

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 params and no output schema, description fully covers what the tool does, what it returns, and when to use it. Sibling list aids context.

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?

No parameters; schema is empty. Description adds value by specifying what fields are returned (name + one-line description), which is not in the schema. Baseline is 4 for 0 parameters, and description meets it.

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?

Clearly states 'List all available skills (name + one-line description only)', specifying verb, resource, and scope. Distinguishes from siblings by noting output brevity and referencing match_skill and get_skill.

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?

Explicitly says 'Cheap to call; use before match_skill or get_skill', providing clear when-to-use context and suggesting sibling tools for more detail.

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