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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them: it names the external provider (Crossref) and discloses the hard result cap of 8 results, which is a behavioral constraint an agent must plan around. It does not mention rate limits or what happens when nothing matches.

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?

One sentence, front-loaded with the verb and data source, then the input modes, then the return shape and cap. Every clause carries information and there is no filler.

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?

With only one parameter and no output schema, the description usefully compensates by naming the returned fields (DOI, authors, year, venue) and the maximum result count. The one notable gap is that the cap of 8 comes with no mention of pagination, offsets, or how to retrieve additional matches.

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% and the single parameter's description already lists 'Title, author names, keywords, or a DOI.' The description merely restates that same enumeration, adding no syntax, format, or precedence guidance (e.g., how to combine author and keyword terms). Baseline 3 applies when the schema does the work.

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?

States a specific verb and resource ('Searches Crossref for published works') plus the accepted input modes and the exact return fields, which separates it from internal-search siblings like search_project or search_all_projects. It stops short of explicitly naming the alternative tools an agent might confuse it with (fetch, search, add_reference).

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 citation-lookup use case is only implied by 'published works' and the DOI/authors/year/venue return shape; there is no explicit when-to-use statement and no routing to alternatives. Nothing tells the agent whether to follow this with add_reference, or to use fetch when a DOI is already known.

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