Resolve collection DOI

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

Discloses key traits: never mints DOIs, uses specific prefix, and does not invent DOIs when none exist. Consistent with readOnlyHint annotation and adds valuable context beyond it.

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?

Four sentences efficiently convey purpose, restrictions, and input guidance. No redundant information.

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?

Fully explains input options, behavioral guarantees, and environmental requirement. Output schema exists, so return values are documented elsewhere.

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 covers all 3 parameters with descriptions. Description adds mutual exclusivity constraint and clarifies behavior for collection/project_code lookups when DOI not found.

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?

Clear verb 'Resolve' and resource 'citation metadata', specifying source (DataCite or doi.org). Distinct from sibling tools which focus on data access or 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?

States read-only, no DOI minting, and an environment variable. Explicitly says to provide exactly one of doi, collection, or project_code. However, lacks explicit comparison to alternatives for resolving DOIs.

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