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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description adds substantial behavioral context beyond that: a hard cost of $0.003, payment instruction handling, no provider account requirement, and a clear metadata-only boundary. This fully discloses what the agent and user should expect from the call.

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?

Three sentences, each earning its place: the first states the core capability and output fields, the second sets the scope boundary (metadata not full text), and the third covers cost and authentication. Front-loaded and free of redundancy.

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?

For a single-parameter read-only tool with no output schema, the description covers everything an agent needs: purpose, result shape, result limit, cost, payment instructions, and auth requirements. Nothing material 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%, so the q parameter is already fully documented as 'Search terms, 2–160 characters.' The description adds a result limit ('up to five') but no additional parameter detail, so a baseline of 3 is appropriate since the schema does the heavy lifting.

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 states a clear verb ('Find'), a specific resource ('publications'), and concrete return fields (DOI identifiers, authors, publication years, citation counts). It also distinguishes itself from related report tools by specifying the publication domain and the metadata-only scope.

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 gives clear context for when to use the tool: when publication metadata is needed, and explicitly says it does not return abstracts or full text, which hints at when not to use it. It does not name alternatives, but the boundary it draws is enough for an agent to route correctly among the many report siblings.

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