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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds useful pricing context ('Free within the daily allowance, then $0.001 USDC per call via x402'), which is beyond what annotations provide and relevant for agent decision-making on cost.

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 short sentences, front-loaded with capability then pricing details. No wasted words.

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 explained. The description covers purpose, performance characteristic, and pricing. It could mention the autocomplete UX expectation (prefix matching, limited results) but is complete enough for a single-param 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?

Only one parameter with 100% schema description coverage ('Partial title'), so the baseline is 3, but the description adds the word 'title' contextually which reinforces the parameter's scope as titles specifically.

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: 'Fast title autocomplete across works.' The adverb 'Fast' signals latency characteristics relevant for autocomplete. However, it doesn't differentiate from siblings like scholarly__works-search, which could be confused with a title autocomplete scenario.

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?

No guidance on when to use autocomplete vs full search (scholarly__works-search) or when partial-title matching is appropriate. Pricing info is provided but that informs cost, not tool selection.

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