List skills

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by stating 'Read-only, free' and explaining what skills are and how they relate to other tools. It does not contradict annotations and gives useful behavioral context beyond the structured data.

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 two sentences with no fluff. It front-loads the core purpose ('List the bundled Hermoso SKILLS') and then adds relevant context and a call-to-action. Every word earns its place, making it highly efficient.

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 parameters and no output schema, the description is complete. It tells the agent exactly what is listed, what those items are, and how to get more detail (get_skill). There is no missing information an agent would need to invoke this tool correctly.

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 tool has zero parameters and the schema is empty with 100% description coverage. Since there are no parameters to explain, the description is not required to add parameter details. The baseline for 0 parameters is 4, and the description fully compensates by explaining what the tool lists and why.

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 the verb 'List' and the resource 'bundled Hermoso SKILLS', and elaborates that these are multi-step workflow instructions (SKILL.md) that orchestrate other tools. This distinguishes it from sibling tools like get_skill and list_playbooks by specifying the exact content being listed.

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 explicit next-step guidance ('Call get_skill to load a bundle'), which helps an agent understand when to use this tool and what to do after. However, it does not explicitly contrast this with other list tools (e.g., list_playbooks, list_creators) or state when NOT to use it, so it falls short of a 5.

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