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

With no annotations provided, the description carries full burden. It describes the tool as a read-only snapshot, implying no side effects. While it doesn't mention rate limits or performance, 'live snapshot' sufficiently conveys non-destructive behavior and immediate data retrieval. Adequate for a stat query.

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 a single sentence with a colon and list, covering all key output categories without redundancy. It is reasonably concise, though slightly run-on. Every part contributes value.

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?

Given no output schema, the description enumerates the major return categories (totals, breakdowns, top lists). This is fairly complete for a stats endpoint. It could mention ordering or freshness, but for a zero-parameter snapshot it is adequate.

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 are zero parameters, so schema description coverage is 100%. The description does not need to add parameter details. Baseline for 0 parameters is 4, and the description adds no extra param info, which is acceptable.

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 provides a 'live snapshot of the indexed MCP ecosystem' with specific data categories (totals, provenance, transport, top-trust lists). The verb 'Get' and resource 'ecosystem stats' are unambiguous. It distinguishes from siblings which focus on individual servers or configurations.

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 phrase 'Live snapshot...' indicates it's for current state data, and the listed breakdowns imply use cases for ecosystem overview. It does not explicitly state when not to use or name alternatives, but the context of sibling tools (e.g., get_server, list_runtimes) suggests when this broader view is appropriate. Minor lack of exclusion criteria.

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