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

Annotations already establish read-only/idempotent/open-world behavior, and the description adds substantial non-obvious context: Bradley-Terry ratings, 95% intervals, tie-aware rank semantics, the provisional flag, the method field, and the endpoint-specific api_key requirement. This is rich behavioral disclosure beyond structured fields.

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?

Purpose is front-loaded in the first sentence, followed by compact paragraphs on return semantics and auth. It is somewhat longer than minimal but each sentence contributes useful context, with no major repetition.

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?

An output schema exists, so return-field details need not be fully repeated, and the description still adds key semantics around uncertainty, rank ties, provisional results, and method. The remaining gaps are parameter details for limit/ranking_id and sibling routing, so it is strong but not fully complete.

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 must carry parameter meaning. It explains api_key behavior (optional on the public endpoint, refused on /mcp/mcp) and maps 'top N' to limit, but gives no default or maximum for limit and no format for ranking_id.

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 first sentence gives a specific verb ('Get') and resource ('top N entities of a ranking') plus the differentiator 'honest uncertainty,' so an agent knows what it returns. It does not explicitly contrast with siblings like aimrank_get_ranking or aimrank_get_crowd_bt, so it is clear but not fully sibling-differentiated.

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 description implies usage by stating it returns top N entities from a ranking, and it notes the api_key requirement on /mcp/mcp. However, it never says when to choose this over sibling ranking tools such as aimrank_get_ranking or aimrank_get_crowd_bt, so routing is left implicit.

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