Lookup DOI

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

Annotations indicate it is read-only, idempotent, and non-destructive. The description adds that it returns full metadata including citations, funding, and license, which is useful beyond annotations. No contradictions.

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 a single, well-structured sentence that conveys the tool's purpose and output in a compact form, front-loading the key verb 'Resolve'.

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 simple parameter (one DOI string), rich annotations, and presence of an output schema, the description sufficiently covers what the tool does and what it returns, leaving no ambiguity.

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?

The single 'doi' parameter is described with examples, adding value beyond the schema. Schema coverage is 100%, and the description reinforces proper usage with sample values.

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 it resolves a DOI to publication metadata, listing specific fields (title, authors, journal, citations, funding, license). This distinguishes it from other education tools by specifying the source (CrossRef) and the type of output.

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 does not provide explicit guidance on when to use this tool over alternatives like education.papers.search or education.pubmed.search. The usage is implied (for DOI resolution), but no exclusion criteria or context is given.

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