Agent Standings check

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: data comes from independent hourly probes, covers live status and 30-day reliability, and returns specific status categories, latency, tool count, schema hash, uptime, incidents, and drift events.

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 compact and front-loaded: the first sentence defines the operation and data source, and the second enumerates returned fields. Every sentence carries useful information with no waste.

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 one-parameter read-only lookup tool with no output schema, the description is complete. It explains the data source, accepted input formats, status values, and the full set of returned fields, leaving no significant gap for correct invocation.

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 100%, so the single parameter is already documented. The description repeats the accepted forms and adds one example ("com.example/server"), which is marginally helpful but largely duplicative of the schema.

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 states a specific operation on a specific resource: live status and 30-day reliability of a public remote MCP server. It is clear what the tool does. It does not explicitly differentiate itself from the only sibling, standings, but the purpose itself is unambiguous.

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 explains accepted input forms (registry name, endpoint URL, host, or short name) and gives an example, which implies how to invoke it. However, it gives no explicit guidance on when to use this tool versus standings, and no exclusions or prerequisites are stated.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that — the ranking order (7-day uptime, then p95 latency) — but does not disclose freshness (how often 'daily' is refreshed), pagination, or caching, which matters for a leaderboard tool.

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?

One sentence, zero filler, and the ranking criteria — the most decision-relevant fact — arrive at the end where they are easy to scan. Nothing is wasted or restated from the title.

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?

With no output schema, the description compensates partially by naming the fields that drive ordering (uptime and p95 latency), so the agent knows roughly what a row contains. It stops short of describing row identity or the shape of the standings, which leaves a small gap for an output-less tool.

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 100% with a documented default of 20 and bounds of 1–100, so the single 'limit' parameter is fully specified in the schema. The description adds nothing about the parameter, which is the correct baseline when the schema does the work.

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 names a specific resource and scope: 'the latest daily standings of tracked MCP servers.' An agent immediately knows this returns a ranked leaderboard rather than a single-tool lookup. It does not explicitly contrast with the sibling check_tool, so it stops short of a 5.

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?

There is no statement of when to call this versus check_tool, and no prerequisites or exclusions. The word 'latest' hints at a snapshot use case, but the agent must infer that this tool is for overview/leaderboard reading while check_tool is for individual inspection.

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