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

With no annotations, the description carries the full burden. It does state the core read behavior ('Return every...') and enumerates the content, but it does not disclose response format, traversal semantics, or whether any setup is needed. Acceptable for a zero-parameter listing tool, but not richly transparent.

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?

A single front-loaded sentence communicates the tool's entire scope with no filler. The colon-separated enumeration is easy to scan and every word earns its place.

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, parameterless discovery tool, the description adequately covers what will be returned (all listed machine-readable surfaces). It is less explicit about the output shape, but the lack of an output schema is partially mitigated by the concrete enumeration.

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?

The tool accepts zero parameters, so there is no parameter meaning for the description to add beyond the empty schema; the 0-parameter baseline of 4 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?

States a specific verb ('Return') and a clearly enumerated resource ('every machine-readable surface' followed by MCP, REST, SKILL.md, AGENTS.md, A2A, x402, CLI, OpenAPI). The scope is broad enough to distinguish this umbrella discovery tool from the more specific sibling tools.

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 word 'every' implies this tool is the umbrella discovery entry point, but the description never explicitly tells an agent when to choose it over siblings like list_mcp_servers or x402_discover. Usage guidance remains implicit rather than stated.

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