list_skills

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It implies a read-only listing operation but does not explicitly state that it has no side effects, what exactly is returned, or any ordering or scope limitations. For a list tool this is a meaningful omission.

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 just two short sentences, both highly informative. It front-loads WHEN and HOW, contains no filler, and every word earns its place. This is an excellent model of concise, scannable tool documentation.

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, parameterless list tool, the description covers the essential use case and even connects to the follow-up tool (read_skill). However, because there is no output schema, a brief note on what the returned list actually contains (e.g., skill names, descriptions) would have made it fully complete.

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 description coverage is 100% by default. The baseline for a zero-parameter tool is 4, and there are no parameter details needed. The description adds no parameter info, but none is required.

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 states a specific verb ('list') and resource ('skills from the repo'), and clearly distinguishes itself from 'read_skill' by noting it is done 'before reading one.' This makes the tool's purpose unmistakable even among many siblings.

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 provides a WHEN condition ('starting an Udon session or discovering available skills') and a HOW sequence ('before reading one with read_skill'). This is direct usage guidance that tells an agent exactly when to invoke this tool and how it fits into a workflow.

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