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

With no annotations, the description carries the full burden and does so well: it discloses auth requirements (Professional+), pay-per-call pricing (depth price less the $0.01 credit), payment channel (USDC on Base/Solana via x402, sent in _meta['x402/payment']), ranking behavior (by impact with curation behind each rank), and an error condition (stale/expired quote refused). This is unusually rich behavioral context.

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?

Purpose and the required quote_id are front-loaded, and the pricing/auth details follow. It's dense but each sentence adds actionable information; the payment mechanics sentence is longer than strictly necessary but still earns its place.

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?

With no output schema, the description usefully covers return content (abstracts present in ~6 in 10 papers, curation behind each rank). It also covers auth, cost, and error behavior. It could say more about the shape of the 'curation' data or pagination, but it's substantially complete for a 2-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?

Schema coverage is 50% (quote_id documented, depth only enum-typed). The description explains quote_id's origin ('from lab_quote') and adds meaning for depth by describing both enum values and what they return (top papers matching the quoted filter, ranked by impact). It compensates well for the undocumented depth parameter.

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 gives a specific verb (get) and resource (papers for a lab_quote) and immediately names the upstream sibling it depends on (lab_quote). It's clear this is a quote-fulfillment retrieval tool, distinguishable from get_subject_papers/get_element_papers, though the tool name 'lab_run' is slightly misleading since nothing is 'run'.

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?

It states the flow (pass the quote_id from lab_quote) and the selecting condition for depth, plus an exclusion (a stale or expired quote is refused). It does not explicitly contrast with the other paper-retrieval siblings, so it stops short of a full when/when-not comparison.

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