list_registries

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

Description says 'list' implying read-only, but annotations have destructiveHint=true contradicting readOnlyHint=true. The description does not disclose potential destructive effects, violating transparency.

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 with an emoji, front-loads purpose, and immediately gives usage context. No redundant 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?

While description covers purpose and usage well, the annotation contradiction (destructiveHint=true vs readOnlyHint=true) introduces confusion about behavior, making it incomplete from a safety perspective.

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?

No parameters exist, so schema coverage is 100%. Baseline for 0 parameters is 4; description adds no param info but none needed.

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 it lists registries and explicitly distinguishes itself from the sibling tool 'search_servers' by saying to use it first to discover registries to search.

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?

Provides explicit instruction: 'Use this FIRST to discover which registries you can search with the 'search_servers' tool.' This gives clear when-to-use guidance and references an alternative tool.

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