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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable context beyond annotations: no auth required, CC0 metadata, and the ~5-day delay between deposit and API appearance. This delay is a behavioral trait that helps set expectations. It doesn't contradict annotations.

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 sentences, each earning its place: what it does, when to use it, and key data-source facts. Front-loaded with the core action and filters, followed by use case and caveats. No redundancy.

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 read-only browse tool with an output schema, the description covers the essential context: purpose, filters, use case, data source, auth, and delay. It doesn't describe pagination or the exact response shape, but the output schema exists and annotations cover safety. Minor gap: no mention of how results are ordered, but this is not critical for a browse tool.

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 100%, so the schema already documents all four parameters. The description adds context about the date-range and member_id filters but doesn't add syntax details beyond the schema. Baseline 3 is appropriate since the schema carries the parameter documentation burden.

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 states a specific verb ('Browse'), a specific resource ('article-to-dataset citation events'), and the key filtering dimensions (creation-date range, publisher member ID). It also explicitly contrasts with needing a known DOI, which distinguishes it from sibling tools like crossref-datacitations.citations.from_article and to_dataset.

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 explicitly states when to use this tool: 'Useful for monitoring newly-deposited data citations from a specific publisher or time window.' It also implies the alternative (needing a known DOI) and names the data source. This gives clear context for selection among the crossref-datacitations siblings.

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