Verify Items

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

Annotations already state readOnlyHint and idempotentHint. The description adds behavioral details: re-resolving DOIs via CrossRef, comparing titles, and reporting specific failure categories (no DOI, unresolved DOIs, mismatches). This goes beyond the structured metadata, so a 4 is warranted.

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 concise and well-structured: a clear purpose statement, a process explanation, and an Args section. No wasted words; each sentence contributes to understanding.

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 low-complexity tool with one optional parameter and an output schema, the description covers the verification logic, reporting categories, and parameter meaning. It isn't missing any critical behavioral or usage information.

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% and the only parameter 'limit' is described in the Args section as 'Number of recent items to check (default 10)', adding meaningful semantics beyond the schema's type/default. This fully compensates for the lack of schema description.

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 verifies recently added items' DOIs against CrossRef metadata, matching title and reporting issues. The verb 'verify' plus specific resource (recently added items) distinguishes it from siblings like get_recent_items or find_duplicates.

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 implies the tool is used after adding items, by specifying 'recently added items' and the verification process. It provides clear context but doesn't explicitly name alternatives or exclusion cases, so it falls just short of a 5.

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