prior_work

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

With no annotations, the description carries the full burden. It discloses the return granularity ('one entry per completed chain'), the key fields including the specially important 'limitations', and a behavioral caution: published chain steps are signed records with URIs and should not be re-derived. It does not mention errors or edge cases, but the read-only nature is clear from 'returns'.

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 description is structured as an opening definition, a detailed output explanation, and a usage paragraph. It is slightly more verbose than strictly necessary, but the additional sentences earn their place by explaining output semantics and use cases. The most important information is 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?

The tool has one parameter and no output schema, so the description must explain both input meaning and return content. It covers input URI semantics, output fields, usage intentions, and a caution about citation. It omits output format and error behavior, but for a simple retrieval tool this is a minor gap.

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 0%, so the description must compensate for the single 'uri' parameter. It does so by specifying that the URI must be a published nanopub URI in a constellation, which gives meaningful domain context beyond the bare parameter name. Exact URI format is not provided, but enough guidance exists for correct invocation.

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 clear statement of what the tool provides: prior claims about a paper, as the starting point for replication or fresh study. It specifies the resource ('published nanopub URI in a constellation') and the output shape ('one entry per completed chain'), making it distinct from sibling validation and lookup tools.

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 tells an agent when to use this tool: to avoid duplicating existing replications, to choose a CiTO relation, and to find still-open parts of a claim. It does not name alternative siblings or state when not to use it, but the usage contexts are concrete and actionable.

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