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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with a pure read. It adds useful context beyond the annotations: what the returned SKILL.md contains (frontmatter name/description plus body), the classification taxonomy, and the presence of required binaries that may need to exist before adoption.

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 sentences, zero filler: the first states what is returned and is front-loaded, the second gives the install procedure. Nothing is repeated from the title or schema, and every clause carries information.

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?

With an output schema present, the description needn't describe return shape, and it still names the notable payload fields and the required binaries. Against a two-parameter read tool with full schema coverage, nothing an agent needs in order to call and use the result is missing.

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 100%, and both parameters are documented in the schema with their provenance from registry_search and the provider auto-resolution order. The description adds no further parameter meaning, so the baseline of 3 applies.

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 uses a specific verb and resource ('Fetch everything an agent needs to adopt a Registry skill') and enumerates exactly what is returned: the full SKILL.md, its classification (prompt-shaped vs scripted vs mcp), and required binaries. This is far more specific than the title alone and tells an agent what payload to expect without opening the output 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?

It gives a concrete next step ('save the returned skill_md as SKILL.md inside a folder named after the slug in your agent's skills directory'), which implies the intended fetch-then-install workflow. However, it never states when to prefer this over adjacent tools such as registry_adopt or registry_search, leaving the agent to infer that search yields slugs and adopt performs installation.

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