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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful return-content context (trust profile and usage stats), but it does not disclose error behavior, required auth, or whether the result includes the full tool definition beyond those fields.

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 one tightly written sentence that states the core action, target resource, identifier types, and return-relevant content. There is no redundant filler or repetition of the schema.

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 one-parameter read-only lookup tool, this description is largely complete. There is no output schema, so the mention of 'trust profile and usage stats' provides useful return-value context; however, it could additionally clarify what is not returned or how failures are reported.

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 the description must compensate for parameter meaning. It mostly restates the parameter name, adding only 'registered ecosystem tool' context. It does not clarify id format, slug format, or where callers can find a valid id/slug.

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 verb (fetch), the resource (one registered ecosystem tool), the selection method (by id or slug), and the contents (including trust profile and usage stats). This distinguishes it from sibling tools like search_tools, list_capabilities, and get_trust_score.

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 gives a clear context: use this tool when you already know the id or slug of a specific tool and need its details. It does not explicitly name alternatives or exclusion conditions, but the 'by id or slug' qualification contrasts with search-oriented sibling tools.

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