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

Annotations cover the safety profile (readOnly, idempotent, openWorld, non-destructive), yet the description adds substantial context beyond them: per-call pricing ($0.002 single, $0.008 batch), the 402 challenge, the prepaid x-credit-token header, no free tier, no API key required, and the returned fields (title, author, publish date). This is exactly the extra behavioral disclosure that annotations cannot carry.

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 core purpose is front-loaded, but the prose is dense, marketing-flavored, and redundant: pricing appears twice ('One URL is $0.002...' and 'Priced $0.002 per call'), and account/auth statements repeat ('no Exa account, no subscription' vs 'No API key required'). Several sentences could be consolidated without losing information.

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 values needn't be spelled out, and the description still covers payment model, auth, batch limits, and content fields. It is essentially complete for a paid read tool, with only minor redundancy rather than missing information.

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%, so the baseline is 3, but the description adds meaning the schema lacks: maxChars range 500..40000 with a default of 8000, and confirmation that urls accepts up to 5 comma-separated values. That is genuine added value over the terse schema descriptions.

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 and resource ('Read a page out of Exa's index') and immediately distinguishes itself from generic fetching ('not off the open web... reads pages a plain server-side GET is blocked from'). An agent can tell it apart from exa_search, web_extract, and url_to_json without opening a schema.

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?

Explicitly routes the workflow: 'Pairs with exa-search: search, then read the winners,' and notes the required input (urls). It gives clear context for when to use it, but does not state exclusions (e.g., when to prefer web_extract or url_to_json instead).

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