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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for going further: it discloses that full text is omitted by default, that long texts are paged, that BibTeX is the default citation format, and that an unknown id returns { error } rather than throwing. That is genuinely useful operational context beyond the 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?

Front-loaded with the resource and its contents, then moving to the high-value behavioral notes (fulltext gating, citation, error case). The opening catalog of linked fields is listy but each clause corresponds to real returned data, so it largely earns its space.

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 no output schema, the description carries the full burden of describing return values and does so thoroughly, including paging behavior for long full texts and the unknown-id error shape. It is nearly complete; only the absence of alternative-tool routing keeps it from the top.

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 100%, so the schema already documents id, citation_format, and the three fulltext parameters, making 3 the baseline. The description confirms defaults (BibTeX, full text off) and adds the paging/error context, but adds little syntax or format detail the schema does not already carry.

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 identifies the resource (a publication) and enumerates what the call returns: metadata, linked entities, conference details, access statements, advisers, links, and a citation export. This is specific enough to distinguish it from search_publications or list_publication_facets, though it never explicitly names those siblings as alternatives.

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?

There is no explicit guidance on when to use get_publication versus search_publications or how to obtain a valid id. The only usage-adjacent content is the note that full text requires include_fulltext=true, which is a parameter behavior rather than a routing rule.

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