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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which conveys safety. However, the description adds no behavioral context beyond what annotations provide—no mention of what data is returned, whether it summarizes multiple entries, or any limitations. Thus, the description contributes nothing beyond the structured metadata.

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 two words long, which is extremely concise, but it is under-specified to the point of being unhelpful. There is no structure or substantive content; it does not convey any information beyond the tool name, so the conciseness is not a virtue but a deficiency.

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?

Despite a simple interface (one required parameter) and strong annotations, the description is too vague to be complete. It does not state the tool's purpose, how the parameter works, or what the output represents. An agent cannot confidently select or call this tool based on the provided description alone.

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%, meaning the 'orcid_id' parameter has no description in the schema. The description 'Employment summary' does not mention the parameter or explain what orcid_id represents or how it is used. This leaves the agent entirely without semantic guidance for populating the parameter, making the tool unusable without external knowledge.

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 'Employment summary' is essentially a restatement of the tool name, adding only the noun 'summary' without specifying an action, resource, or scope. It does not clarify what function it performs (e.g., 'Retrieve employment history for an ORCID record') and fails to distinguish it from sibling tools like 'work' or 'education'.

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, what scenarios it applies to, or how it differs from alternatives such as 'work' or 'works'. The description gives no context for selection, leaving the agent to infer usage from the tool name and parameter.

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