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

Annotations only declare readOnly and openWorld; the description adds genuinely useful context the annotations cannot: no API key needed, the hard top-30 cap on the public table, a $0.002 USDC x402 charge per successful call across Base/Solana/Arc, and that failed calls are free. It stops short of rate limits or freshness/update cadence, but this is well above the annotation baseline.

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?

Front-loaded with what the tool returns, then the access constraint, then the price — a sensible information order in essentially one dense sentence. The field enumeration is slightly list-like but every item is meaningful.

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?

With an output schema present, return values need not be re-explained, yet the description still names the fields; pricing and the top-30 ceiling cover the main operational unknowns. Nothing critical is missing for a one-parameter read tool.

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% with a single optional `limit` parameter already documented as 1–30 with a default of 10. The description's 'top 30 only' corroborates the cap but adds no new syntax or default detail, so the baseline 3 applies.

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?

States a specific verb/resource pair — the ShanghaiRanking ARWU 2026 world university ranking — and enumerates the returned fields (position, institution, national rank, score, six indicators). It does not, however, distinguish itself from close siblings like search_shanghai_gras_rankings or search_university_rankings_mega_pack, so an agent must infer which ranking product is which.

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 notes the public page shows only the top 30, which hints at a scope limit, but it never says when to pick this over the GRAS or mega-pack ranking tools, nor what to do if more than 30 entries are needed. Usage is left to inference.

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