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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: ~130k skill index, security-gate screening that withholds failing skills, temporary loading with no permanent install, and version-pinned loading behavior. It also advises reading third-party instructions before following them, which is meaningful safety guidance for executing external content.

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?

Front-loaded with the core action and prerequisite, then edge-case parameters, then a safety admonition. Dense but every sentence carries information; the catalog-size and screening sentence is slightly ornate but justifies the security posture.

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 7-param, no-output-schema tool, it covers purpose, sourcing, pagination, version pinning, and safety caveats. It stops short of describing what a successful load returns (skill body vs. files, truncation behavior), which is the main remaining gap given no output 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 coverage is 100%, so baseline is 3, but the description adds real semantics: file must be paired with the original request_id from the same scanned version, and page fetches additional content of a named file. It does not explain skill vs source vs version pairing in prose, leaving some of the 7 params to the schema.

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?

States a specific verb+resource ('Load a selected skill returned by find_skill for this task') and explicitly ties it to the sibling tool that produces its input, so an agent can distinguish it from find_skill or scan_skill without opening a schema.

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?

Names the prerequisite (a skill returned by find_skill) and gives concrete routing for edge cases: pass file + original request_id for a single named file, page for more content. It lacks an explicit 'do not call before find_skill' prohibition or guidance versus scan_skill, but the usage context is clear.

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