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

No annotations are provided, so the description carries the full burden. It usefully discloses the paid model (0.002 USDC per call via x402) and the return payload, but says nothing about rate limits, error behavior, or empty-result handling; the 402 handshake is largely covered by the paymentProof schema description.

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 tight sentences, zero waste: capability and return shape first, pricing second. Nothing repeated or padded.

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?

For a stateless search tool with no annotations or output schema, the description covers what it does, what comes back, and the cost model. It lacks only details like result pagination or max result behavior, which the schema partially implies via limit.

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 75% and the only undocumented parameter is limit, whose 1-30 bounds are still in the schema. The description clarifies the sort semantics (relevance vs submission date), which is a modest addition; baseline 3 applies given the high coverage.

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 (searches) and resource (arXiv), plus the two sort modes and the exact fields returned. No sibling tool overlaps arXiv literature search, so the agent can select it unambiguously.

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?

Usage is implied by the resource name – an agent looking for academic papers will pick it – but there is no explicit when-to-use/when-not guidance or comparison to alternatives like wikipedia or web_extract.

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