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

No annotations exist, so the description carries the full behavioral burden, yet it discloses nothing about ordering semantics, tie-breaking, how many agents are returned by default, or failure behavior for an unrecognized metric. It mentions ranking but not what the returned entry actually contains, and there is no output schema to compensate.

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 short sentence with no filler, and the ranking concept is front-loaded. It is not under-specified to the point of being useless, though it is sparse for a tool with zero annotation coverage.

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?

This is a simple two-parameter read tool whose schema is fully documented and has no output schema, so a short description is defensible. Still, it omits what the ranking is drawn from and what the returned entries include, which an agent calling it cold would want to know.

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%; both parameters are documented with the metric allowed values and the limit default of 10. The description adds only that 'metric' is the ranking key, which is a marginal gain over the schema. Baseline 3 applies since 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?

A specific verb+resource ('Get top agents') plus a scope qualifier ('ranked by metric') makes the operation unambiguous. However, it gives no signal distinguishing it from siblings like list_agents or search_agents, so an agent cannot tell from the description alone why it would choose this over a ranked 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?

There is no statement of when to use this tool, when not to, or which sibling (list_agents, search_agents) is the alternative. The agent must infer usage entirely from the name.

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