get_work_by_doi

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

No annotations are provided, so the description is fully responsible for behavioral disclosure. It explains accepted DOI formats and the returned dictionary fields, which is useful, but it does not mention error behavior, missing metadata, or any side effects.

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, front-loaded sections with no wasted words. The purpose is stated first, followed by args and returns, both of which earn their place.

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 lookup tool, the description provides enough context: what the tool does, what the parameter expects, and what the return value contains. The output schema exists, so return-value detail in the description is a bonus.

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 coverage is 0%, but the description fully documents the single doi parameter with a concrete example, the full URL alternative, and its role. This adds substantial meaning beyond the mere property name 'Doi'.

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 opens with a specific verb+resource: 'Retrieve bibliographic metadata for a single work by its DOI.' It clearly differentiates from the sibling search_works by emphasizing single-work lookup via DOI rather than general search.

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 context is clear: use this when you have a DOI and need metadata for one specific work. It stops short of explicitly naming alternatives or saying when not to use it, but the single-work framing implicitly distinguishes it from search_works.

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