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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, and the description does not contradict them. The description adds substantial behavioral context beyond annotations, including the payment requirement, the payment_required fallback flow with specific sibling calls (fillin_probe, fillin_signup, fillin_payment_challenge), and the free probe limit, which are critical for invoking the tool correctly.

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 well-structured: a concise definition up front, a clear usage trigger, then detailed payment instructions. Each section adds necessary information and there is no filler, though the payment block is dense and could be considered dense but necessary.

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?

Given the tool has an output schema, return-value details are not required. The description covers what the tool does, its sources, when to use it, and the full payment/auth flow, making it complete enough for an agent to select and invoke the tool correctly.

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 schema already documents query, cutoff, and k, including types and constraints. The description adds little parameter-specific meaning beyond the schema; for example, 'Daily snapshot' hints at the cutoff's time-window semantics but does not elaborate on parameter formats or interactions.

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 opens with a specific verb-resource statement: 'Daily snapshot of new research relevant to AI/ML/agents' and enumerates exact sources (arXiv categories, HuggingFace daily papers, bioRxiv), making it immediately clear what the tool queries. This clearly distinguishes it from sibling tools like query_cves and query_markets, which target different domains.

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 explicitly states when to use it: 'Use when a user asks about a new technique, paper, or benchmark.' It does not explicitly mention sibling alternatives or negative usage conditions, but the trigger condition is clear and sufficient for an agent to select this tool among research-oriented tools.

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