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

The description reveals key behavioral aspects: it is keyless and has a cost per call. It also indirectly implies a read-only operation, but it does not explicitly state side effects, rate limits, or potential error conditions. Without annotations, this leaves some behavioral aspects undisclosed.

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?

The description is moderately concise, including necessary details about input types, output, pricing, and an example. It is well-structured, though slightly verbose with repeated mentions of the identifier sources.

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 the minimal schema, the description provides essential context: what the tool does, what inputs it accepts, and what output to expect. It omits edge-case handling, but that is not critical for a typical tool description.

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?

Although the schema only reveals a generic 'params' object with no defined properties, the description explains that it expects 'id' or 'doi' keys and elaborates on the accepted identifier formats. This adds significant meaning beyond the schema, though it could be more explicit about the alias relationship.

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 the tool's purpose: retrieving full text and open-access PDFs for a paper using various identifiers. It explicitly mentions the output format (sections, PDF location) and distinguishes it as a post-search retrieval tool, making its role unambiguous.

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 provides usage guidance by describing the tool as 'the now read it call after a paper search' and listing accepted identifier types. However, it does not explicitly mention alternative tools or when to prefer them, but the contextual hint is sufficient for most use cases.

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