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

With no annotations, the description carries the full load and does so richly: dropped non-element/non-topic words, wildcard expansion into unrelated fields, reading `warnings` for dropped terms/abbreviations/expansions, account requirements (Professional+), and pay-per-call pricing with exact rails (_meta x402, $0.01 USDC on Base/Solana). This goes well beyond what the schema reveals.

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?

It is front-loaded with the syntax, which is good, but it is dense and packs syntax, warnings behavior, return shape, best-practice sizing, account tier, and payment rails into one long paragraph. The syntax example is valuable but the whole is crowded.

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 no output schema, the description does describe returns (match counts by year and community, nearest broader query on no match, quote_id). Combined with the warnings guidance and pricing/account requirements, an agent has enough to call it correctly, though the syntax could use a tighter spec.

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 two parameters (query, markdown) are already documented. The description explains the query syntax and the markdown-alternative use of a fenced block, but since the schema fully documents both, this is baseline territory.

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 clearly states this is a query-scoping/counting tool via a specific boolean filter syntax over element symbols and topic names. It distinguishes itself from get_element_papers/search_subjects by being a scoping step that produces a quote_id for lab_run. The verb 'scope' is a bit abstract but the resource and output are concrete.

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 gives explicit usage direction: narrow filters (two elements + one topic) work best, read `warnings` first, and mentions the lab_run handoff that turns a quote_id into ranked papers. It doesn't explicitly contrast against the get_* siblings, but the scoping-to-lab_run flow makes its role clear.

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