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

Annotations include readOnlyHint=true, and the description reinforces this by saying 'Public-safe latest status only'. It adds context beyond annotations by stating 'not an endorsement'. No contradiction.

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 concise sentences, no filler. Each sentence adds value: first states action and resource, second adds qualifiers.

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?

Tool has no output schema and few parameters. The description covers purpose and behavioral limits but does not describe the return value or structure of the registry entry. While adequate for a simple lookup, more detail on output would improve completeness.

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?

Parameter names (url, mcp_id) are self-explanatory, and the description mentions 'MCP URL or mcp_id' implying they are alternative identifiers. However, with 0% schema description coverage, the description could have explained each parameter's format or constraints more thoroughly.

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 tool's purpose: to look up a public MCP Registry entry using either a URL or mcp_id. It specifies the resource and action, distinguishing it from sibling tools like lookup_passport or lookup_readiness.

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 indicates when to use ('public-safe latest status') and what it is not ('not an endorsement'). While it does not explicitly list alternatives or when not to use, the context is adequate for an agent to decide.

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