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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real value beyond them: it discloses the exact response content — service identity, DOI, per-dataset authors, and both text and BibTeX renderings. Nothing is said about partial/no-match inputs, which is the only notable gap.

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 two-sentence structure is front-loaded with the core purpose, but the second sentence repeats the first (the service name, maker, address and paper are stated twice in near-identical terms), and the run-on enumeration of fields makes it harder to scan than necessary.

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 zero-required-parameter read tool with no output schema, the description is nearly sufficient: it enumerates return content and covers every input combination including the empty case. Only the naming/format of the citation keys and behavior on unknown card or solver names is left unstated.

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 67% and the 'card' property has no schema description at all, so the description has to carry some weight. It does clarify the domain+card pairing versus solver-as-substitute and the zero-argument case, but 'card' itself is never defined beyond the pairing hint, leaving that gap only partly filled.

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?

Specific verb+resource: it says the tool returns citation information for a card, a solver, or the service itself, and even previews the citation contents (service, DOI, measurement authors). It is clearly distinguishable in substance from describe_card/describe_solver, but it never names those siblings to draw the contrast explicitly.

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?

Usage is only implied: the parameter mapping ('With domain and card, or solver... with neither, it is how to cite the service itself') tells the agent how inputs select the answer, but there is no statement of when to reach for this tool rather than describe_card, describe_solver, or find_model, despite those being plausible confusions.

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