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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds valuable behavioral context beyond that: api_key optionality and refusal on /mcp/mcp, plus the embedding of share assets so results can be handed as clickable links. No contradictions.

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?

The description is compact yet dense: a clear purpose, a terse list of filter constraints with enums, a practical note about share assets, and an auth caveat. Every sentence carries useful information with no filler.

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?

Given the output schema exists (handling return values) and annotations cover open-world/read-only/idempotent behavior, the description is fairly complete. It addresses authentication, parameter domains, and result embeddability. The only gap is that 'category' values are not enumerated, but for an open-world browsing tool this may be intentional.

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 0%, so the description must compensate. It lists the filters category, media_type with explicit allowed values, sort with explicit values, limit range 1-50, and notes api_key optionality. It does not detail category values, which remain open-ended, but overall it provides substantial semantic meaning beyond the bare 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 clearly states the verb 'browse' and the resource 'public rankings', with the analogy 'surfing aimrank.io' that conveys discovery. It distinguishes from sibling tools like get_ranking/get_leaderboard by framing this as a public browsing/discovery tool, not a targeted fetch.

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 a browsing/discovery use case ('surfing aimrank.io') with filters, but it does not explicitly state when to prefer this tool over siblings or when not to use it. It provides context about the public endpoint and auth quirks, but no exclusionary guidance.

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