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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds the time window ('this month'), ordering ('in order'), and auth context ('No API key needed'). It does not describe response fields or pagination, but with annotations covering safety and no output schema, this is still fairly 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?

The description is a single front-loaded sentence with no wasted wording. Each clause contributes useful information: timeframe, game scope, ordering, and auth requirement.

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 read-only ranking endpoint with rich annotations and full schema coverage, the description supplies the key context an agent needs: timeframe, scope, ordering, and no API key requirement. Although there is no output schema, the return shape is inferable as an ordered list of top-voted servers.

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 100%, so the schema already documents the game enum and limit range/default. The description adds that omitting the game means across all games and that results are ordered, but it adds no further syntax or semantics for limit. Baseline 3 is appropriate when the schema does the heavy lifting.

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 resource and ranking: 'most voted servers this month', with the scope 'one game or across all games' and 'in order'. This clearly distinguishes it from get_server and search_servers by being a ranked list rather than a lookup or 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?

It explains the parameterized scope (one game versus all games) and notes 'No API key needed', which gives useful context. However, it does not explicitly say when to use this instead of siblings like search_servers or recent_votes, and it gives no exclusions.

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