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

The description discloses genuinely useful behavior beyond the schema: left/right order is randomised, match_quality measures closeness only and is not a predicted winner, and api_key is optional on the public endpoint but refused on /mcp/mcp. However, 'next pair' plus randomised ordering implies state progression and non-identical repeat results, which sits uneasily with the declared idempotentHint=true.

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 purpose is front-loaded in one line, followed by a compact strategy list and two short behavioral notes. The strategy enumeration is long but each value carries selection information; no sentence is filler.

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 an output schema present, the description needn't explain return values, and annotations cover the safety profile. What remains necessary for correct invocation — strategy choice, auth requirement per endpoint, and how to present the pair — is all covered; only ranking_id's semantics and the relationship to aimrank_get_daily_pair are missing.

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 coverage is 0%, so the description has to compensate, and it largely does: it lists all seven strategy values with the default (adaptive), and explains api_key's conditional requirement across the public endpoint versus /mcp/mcp. Only ranking_id is left unexplained, though its role is inferable from the tool purpose.

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 and resource: 'Get the next pair of entities to evaluate.' It also implicitly separates itself from aimrank_predict_matchup_winner by noting the pair arrives with 'no rating or predicted winner'. It doesn't explicitly name aimrank_get_daily_pair as the alternative for a scheduled pair, so sibling differentiation is only partial.

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?

It gives clear operational guidance for the result ('show it to the voter as-is') and enumerates the available strategies with a stated default, which is useful context. However, it never says when to choose this tool over aimrank_get_daily_pair or aimrank_predict_matchup_winner, and no exclusion criteria are given.

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