get_publication

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

The description makes the read-only fetch behavior clear and discloses the meaningful return additions (abstract, DOI, galleys with public links). It doesn't mention authentication or error behavior, but nothing suggests side effects.

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 first sentence states the operation and scope; each following sentence adds needed context without filler. Compact and front-loaded.

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?

Provides the retrieval path from get_submissionainer, the meaning of publication, and the distinguishing return fields. Left uncovered: the optional journal parameter, and explicit notes on permissions or failure/empty states.

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?

The description explains the publication parameter well, including how to obtain it from get_submission. It also implies what submission refers to, but it never explains the optional journal parameter, and with 0% schema coverage, that remains a gap.

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 opens with a precise action and object: fetch one version of a submission. It explicitly defines 'publication' as a version and contrasts this endpoint's full-detail return with the trimmed list, making its purpose unambiguous.

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?

It explains the correct call flow (find the publication ID via get_submission) and what additional data this endpoint provides. It does not explicitly name a “don’t use when” scenario, but provides clear context for when this endpoint is appropriate.

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