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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description correctly avoids restating them. It adds valuable context about api_key behavior (optional on public endpoint, refused on /mcp/mcp), which is not covered by annotations and is critical for successful invocation.

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 sentences with zero filler. The core purpose is front-loaded in the first sentence, and the second sentence adds a critical behavioral detail. Every word 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?

The description covers the key behavior (metadata + top 25 sorted by rating) and the api_key nuance. An output schema exists, so return values are handled there. It is complete enough for an agent to call the tool correctly, though it could mention what 'metadata' includes.

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 compensate. It explains api_key's optionality and endpoint-specific behavior, which adds meaning beyond the schema. However, ranking_id is not explicitly described, though its purpose is clear from the name and the tool's purpose. The compensation is partial but adequate.

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 clearly states a specific verb (Fetch) and resource (ranking's metadata + top 25 entities sorted by rating). It precisely distinguishes this tool from siblings like aimrank_get_leaderboard or aimrank_get_ceiling by specifying the exact output scope.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention any exclusions or conditions that would route an agent to a sibling tool, leaving the agent to infer usage from the name and purpose alone.

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