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

Annotations already declare readOnlyHint and openWorldHint. The description adds important behavioral context beyond annotations: a $0.003 USDC cost per successful call, x402 payment across Base, Solana, or Arc, and no charge for failed calls. It does not discuss rate limits or authentication beyond payment.

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 front-loaded with sources and data fields, followed by search options and pricing. The parenthetical field inventory is dense but useful for understanding what the rankings include; overall it is appropriately sized.

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 and complete parameter schemas, the description needs to explain sources, scope, search behavior, and cost. It covers ARWU/THE coverage, available metrics, search dimensions, year selection, and payment terms, leaving no critical invocation gap.

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 description coverage is 100%, so the schema already documents limit, country, theYear, arwuYear, and university with examples. The description only restates that users may search by university name and/or country and select years, adding little beyond 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 states a specific verb and resource: searching university rankings side by side from ARWU and THE. Naming both sources helps distinguish it from single-source siblings like search_shanghai_arwu_rankings, though it does not explicitly frame the distinction.

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?

It says to search by university name and/or country and that years are selectable, which implies basic usage. However, it never states when to choose this combined rankings tool over siblings such as search_shanghai_arwu_rankings or search_leiden_ranking, nor any exclusions.

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