List skills

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

Annotations already declare readOnlyHint=true and idempotentHint=true, signaling a safe operation. Description adds that returned items are readable via skill_read, but does not disclose deeper behavior such as input format or pagination on a simple zero-parameter tools.

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 one efficient sentence with no fluff. It front-loads the action, defines the resource, and closes with a useful pointer to skill_read.

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 zero-parameter list tool, the description is complete: it says what is listed, why it matters, and how to continue with skill_read. Annotations cover safety, and no output schema is needed for this simple listing.

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?

Tool receives no parameters, so semantic explanation is unnecessary. The schema description coverage is 100%, and this zero-parameter context gives the tool the baseline 4.

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?

Description states 'List available skills' with a specific verb and resource, and clarifies skills are 'guidance playbooks' for using the server. It is clearly distinguished from sibling tools like find_images and skill_read.

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?

Description gives the clear context: use it to see what guidance is available before reading a skill. It points to skill_read as the follow-up action, though it does not explicitly state when not to use this tool.

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