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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds that the tool returns 'summaries' and includes 'put-codes', which is useful behavioral detail, but it does not describe pagination, ordering, or what constitutes a 'summary'.

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 extremely short, which is efficient, but it is under-specified to the point of being vague. It reads as a fragment rather than a complete sentence, providing minimal actionable information. This is under-specification rather than purposeful conciseness.

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?

While the tool has an output schema and strong annotations, the description itself is insufficient. It does not state that an ORCID iD is required, how the summaries are structured, or what 'put-codes' means in this context. The description alone would not allow an agent to confidently invoke the tool correctly.

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 description coverage is 0%, and the description does not explain the 'orcid_id' parameter at all. It only mentions 'works' and 'put-codes', leaving the parameter semantics entirely to inference from the parameter name. The description fails to compensate for the lack of schema documentation.

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 identifies the resource ('Works (publication)') and mentions 'put-codes', but lacks an explicit verb like 'retrieve' or 'list'. It vaguely suggests returning summaries of publications for a person, but does not clearly distinguish from sibling tools like 'work' or 'record'.

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 guidance on when to use this tool versus alternatives. No mention of required context, prerequisites, or exclusions. The sibling tool 'work' likely serves a similar purpose, but no differentiation is provided.

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