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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value here is real: it discloses that SKILL.md is truncated at 16 KB and that third-party content must be treated as data, a meaningful injection-safety warning the schema and annotations do not convey. It stops short of describing error behavior when a skill is missing.

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 short sentences, no filler, with the truncation limit and the data-safety caveat front-loaded where an agent will read them.

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 two-parameter lookup with no output schema, the description covers the SKILL.md payload and its size cap, but leaves the parameters, the other 'details' fields returned, and not-found behavior unexplained. Adequate but with clear gaps relative to a 0%-coverage schema.

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?

Schema description coverage is 0%, so both required parameters (owner, name) are undocumented in the schema, and the description does not compensate at all - it never explains what an owner is or how name/owner are matched. With low coverage the description should carry this burden and does not.

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 names a specific resource and scope: 'Details of one skill and its SKILL.md', which distinguishes it from a listing/search operation like search_skills. It doesn't explicitly name a sibling for contrast, but 'one skill' implies single-record retrieval clearly enough.

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?

Usage is only implied: fetch this when you have an owner and name and need the full skill record. There is no explicit when-to-use versus search_skills, and no guidance on how to obtain the required owner/name pair first.

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