get_doi

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

Description implies a read operation but does not explicitly state idempotency, auth requirements, or side effects. With no annotations, the agent lacks clarity on safety.

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 sentences, front-loaded with the main purpose, and no redundant information. Every sentence adds value.

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?

Covers the tool's core functionality and optional parameter. Lacks details on return structure or error handling, but for a simple retrieval tool with no output schema, it is adequately complete.

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?

Adds meaningful context for the 'doi' parameter by noting accepted formats (bare, URL, doi: prefix), and for 'include_xml' by explaining it returns raw DataCite XML. Schema coverage is 0%, so description compensates well.

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?

Clearly states 'Retrieve complete metadata for a single DOI', which is a specific verb+resource. Distinguishes from siblings like search_dois (search) and get_doi_metrics (metrics) by focusing on single DOI metadata retrieval.

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?

No guidance on when to use vs alternatives. Only provides a tip on accepted DOI formats, but does not mention related tools or conditions for use.

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