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

With annotations absent, the description carries the burden. It discloses the output types and the engines parameter behavior (comma-separated subset), but does not mention potential side effects, rate limits, error handling, or whether it performs network calls. The description provides some behavioral context but lacks depth.

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 two sentences, front-loaded with the primary purpose, followed by necessary engine instructions. Every word earns its place, with no redundant or incidental content.

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?

An output schema exists, so return values need not be detailed. The tool is simple with only one required parameter. However, the description lacks explicit context about when to use this tool versus siblings, and does not mention what happens if the DOI is invalid or not found. Overall it is reasonably complete for a lookup tool but has minor gaps.

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 description coverage is 0%, so the description must compensate. It explains the 'engines' parameter with a concrete list of valid values, but for 'doi' it only says 'known DOI' without defining format or validation. The description adds partial meaning but does not fully compensate for the missing schema descriptions.

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 function with a specific verb ('Enrich') and resource ('one known DOI'), and lists the types of output (metadata, reading links, full-text availability signals). This distinguishes it from sibling tools like search or abstract.

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 phrase 'one known DOI' implies the tool is for when you already have a DOI, but it does not explicitly mention when not to use it or suggest alternatives like scholarfetch_search for finding DOIs. The engines parameter guidance is useful but does not cover when to choose this tool over siblings.

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