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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds useful behavior: results are pre-sorted and each row carries the source's own rank and the comparison population, but it omits defaults for limit/order and any pagination or error behavior.

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?

Two tight sentences, front-loaded with the core operation before the input requirement. No wasted wording, though it is brief enough to leave key semantics unstated.

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 6 parameters, 0% schema coverage, no output schema, and only 1 required field, the description is too thin: it explains the general shape of the result but not the filter parameters or enum meanings needed to invoke the tool correctly.

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 0%, so the description must carry the param burden, yet it only implies metric and season. limit, order, position, and especially the 10-value entity_kind enum are left entirely unexplained, so an agent cannot reliably use half the parameters.

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 operation: 'Top entities on one verified metric for one season,' which is a clear verb+resource and implies a leaderboard/ranking tool. It does not explicitly contrast with siblings like run_stat_query or get_entity_metrics, so the boundary is only partially drawn.

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?

'Takes a verified panel metric key' implies a prerequisite (the metric must be verified/panel-scoped), which hints at when this tool applies. However, it never states when to choose this over run_stat_query or get_entity_metrics, leaving the selection to inference.

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