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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds substantive behavior beyond that: AI-based query decomposition, a 7-day default window, a 12-month max lookback, newest-first ordering, and a 50-result cap. It omits auth/rate-limit context, so it stops short of the richest tier.

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?

Front-loads purpose, then routing, then behavioral constraints, then examples. Slightly redundant because its query examples repeat the schema's examples verbatim, but every sentence still carries routing or constraint value.

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?

No output schema exists, yet the description discloses ordering, result cap, and default time window, so an agent knows what to expect on return. Combined with the clear sibling routing, nothing needed to call this correctly is missing.

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%, and the description's parameter-relevant facts (7-day default, 12-month lookback, 50 max results, AI query decomposition) largely duplicate what the schema already documents. Baseline 3 applies since the schema carries the parameter burden.

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 (search quantum computing research papers from arXiv) and explicitly contrasts with sibling tools searchJobs and searchCollaborators. An agent can distinguish this from getLatestPapers and getPaperDetails purely from the description.

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?

Gives explicit when-to-use triggers ('recent research, specific papers, or academic topics'), explicit exclusions with named alternatives ('NOT for jobs (use searchJobs) or researcher profiles (use searchCollaborators)'), and routes to getPaperDetails for full abstracts. Nothing is left to inference.

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