get_doi

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

No annotations provided. The description details the return object (full Unpaywall DOI object) but does not mention rate limits, authentication, or error handling. It assumes a read-only operation but does not confirm.

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 concise sentences with examples; 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?

The description, combined with an output schema, adequately covers the tool's behavior for a simple single-DOI lookup. Lacks details on error scenarios but sufficient for basic usage.

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?

With only one parameter 'doi' and 0% schema description coverage, the description provides examples but does not specify required format, validation, or constraints beyond being a string.

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 looks up Open Access status and bibliographic metadata for a single DOI, and distinguishes from the sibling tool 'search_articles' which is for searching multiple articles.

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 indicates use for a single DOI with examples, but does not explicitly state when not to use or alternative scenarios. The sibling tool name 'search_articles' provides implicit contrast.

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