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

The description discloses that only id, name, and description are returned, not the full body, and that load_skill is needed for the body. Combined with the readOnlyHint annotation, behavior is reasonably transparent, though pagination or ordering are not mentioned.

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 a single, focused sentence that states the purpose, output shape, and relationship to load_skill without unnecessary detail or repetition.

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 the tool has no parameters and is a simple read-only listing operation, the description contains all necessary context: what is listed, what fields are returned, and how to get more detail. No additional information is needed.

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 no parameters, and the description introduces no ambiguous parameter expectations. Since there is no input schema to elaborate on, parameter semantics are fully covered.

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 tool lists reusable skills and specifies the returned fields (id, name, description). It also distinguishes this tool from load_skill by noting the body is fetched separately.

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 implies the primary use case is to enumerate available skills before loading one, and points to load_skill for full body retrieval. However, it does not explicitly mention when not to use this tool or compare it to other listing tools.

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