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

With no annotations, the description carries the full burden and discloses only the 1-credit cost. It does not state read-only behavior, what happens for an unknown or malformed DOI, whether the call fails or returns an empty payload, or any rate limits.

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 short fragments with no wasted words, but the brevity comes at the cost of under-specification rather than disciplined concision. The cost note is front-loaded well but sits alongside a bare noun phrase rather than a complete statement of action.

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 tool with no annotations and no output schema, the description should say what metadata is returned (title, authors, citation counts?) and how failures surface. Neither is covered, so an agent knows the input but not what it will get back or how errors behave.

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 100%, so the single 'doi' parameter is technically documented, but the schema text is only 'string, required'. The description adds that the value must be a DOI resolvable via Crossref, which is a marginal but real clarification beyond the schema.

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 fragment 'Metadata for a DOI from Crossref' identifies the resource and data source, but relies on the tool name for the verb 'lookup'. It does not explicitly contrast itself with siblings like papers_search or arxiv_search, which an agent might reasonably pick for a similar metadata-fetching task.

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 when-to-use guidance is given: nothing says to call this only when a DOI is already known, or to use one of the search siblings when only a title/author is available. The credit cost note hints at frugality but is not usage direction.

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