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

Annotations already declare readOnlyHint=false, openWorldHint=true, and non-idempotence. The description adds the metering/pricing trait, which is genuinely useful context beyond the annotations, but it does not explain the unusual readOnlyHint=false for a search nor disclose anything about rate limits or quota-exhaustion behavior.

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 parenthetical sentences, zero filler, with the core capability front-loaded and the metering caveat last. Every clause 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, listing the returned fields (DOI, venue, citation counts, retraction flags) is the right compensation, and the metering note covers the cost dimension. It could still say a bit more about result limits/pagination and the DOI single-lookup mode, but the essentials are present.

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%, so query, doi, and limit are fully documented in the schema. The description only reinforces the payload fields and hints at DOI lookup; it adds no syntax, format, or behavioral meaning beyond the schema, so the baseline 3 applies.

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 (Search) plus resource (scholarly works) and enumerates the return payload (DOI, venue, citation counts, retraction flags). It is clear what the tool does, but it never names a sibling such as verify_citations or check_source to route the agent among the other scholarly tools.

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?

"Metered after the monthly free allowance" warns about cost but gives no when-to-use, when-not-to-use, or alternative-selection guidance. Nothing tells the agent whether to prefer this over verify_citations, check_source, or search_claims.

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