Get Researcher Published Works

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

Annotations already declare the operation is read-only, idempotent, and non-destructive. The description adds useful context by specifying 'public ORCID data' and naming the source (pub.orcid.org), plus clarifying the exact types of identifiers returned (DOI/other external identifiers). This goes beyond the annotation hints without contradicting them.

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 a single concise sentence that front-loads the core action and resource, then lists the included fields. Every part contributes useful information, and there is no repetition or 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?

Given the tool has only one parameter, a well-covered schema, an output schema, and strong annotations, the description is complete. It communicates the source, scope, and included data fields, while the schema and annotations cover the remaining invocation details.

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 schema already provides 100% coverage for the single parameter, including format and an example. The main description doesn't add significant new meaning about the parameter itself, but the schema's own description is adequate, so the baseline score of 3 is appropriate.

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 states the tool retrieves 'the list of publications and other works recorded on a researcher's ORCID profile' and enumerates key fields like title, work type, journal title, publication date, and identifiers. It is specific and distinguishable from siblings such as orcid.researcher.profile or orcid.researcher.search, though it does not explicitly contrast itself with them.

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 implies usage when a list of a researcher's publications or works is needed, and the schema notes the orcid_id can be obtained from orcid.search_researcher. However, it does not explicitly state when to use this tool versus alternatives like orcid.researcher.profile, nor provide exclusion criteria.

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