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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false. The description still adds value by explicitly disclaiming side effects ('does not install or execute anything') and by naming the returned content, which annotations do not cover.

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 tight sentences with the returned content front-loaded and the negative constraint second. Nothing is wasted and no filler.

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?

No output schema exists, so the description correctly names the return payload, and the read-only nature is double-covered by annotations. Only the ID format and acquisition path are left implicit, a minor gap for a single-parameter lookup.

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?

There is one required parameter with 0% schema description coverage, so the description must carry the load. It does explain that 'id' means a catalog ID, but says nothing about the required 16-hex-character format or where the ID comes from, leaving part of the gap unaddressed.

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 gives a specific verb+resource and enumerates the payload (compatibility evidence, freshness, upstream setup link) keyed by catalog ID. 'By its catalog ID' implicitly separates it from the search/recommend siblings, but no sibling is named explicitly, so it falls just short of a 5.

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?

'By its catalog ID' implies the caller must already hold an ID, presumably obtained from search_resources or recommend_resources, and 'Does not install or execute anything' bounds the scope. However, neither the when-to-use condition nor an alternative tool is stated outright, leaving usage to inference.

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