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

Annotations already indicate read-only, idempotent, open-world behavior, and the description adds actionable auth context: api_key is optional on the public endpoint but required on /mcp/mcp. It also exposes the rating-based ordering semantics. No contradiction with annotations.

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 short sentences with the core purpose front-loaded and the auth caveat separated. Every phrase earns its place.

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 leaderboard tool, the description plus output schema covers purpose, ordering, and auth behavior. It could name a sibling alternative or state how rankings are identified, but nothing essential is missing for a basic call.

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?

With 0% schema description coverage, the description compensates well: 'top N' communicates the limit parameter, 'of a ranking' ties to ranking_id, and the api_key sentence explains its optionality and endpoint-specific requirement. Only the default behavior of limit is left to 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 uses a specific verb-object pair ('Get the top N entities of a ranking') and defines the sort order ('sorted by rating'), so an agent can tell it apart from sibling tools like aimrank_get_ranking. The scope 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 wording implies using this when the top-scored entities of a ranking are needed, but it never states when not to use it or names alternatives. Context is inferred from the purpose rather than explicit routing guidance.

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