get_work

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

Discloses that ambiguous titles will not silently take the top1 result, which is a useful behavioral detail. However, with no annotations present, the description should also cover other traits like error handling or authentication but does not.

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?

Two sentences with front-loaded purpose. No wasted words, but could benefit from adding parameter explanations without becoming verbose.

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?

Output schema exists so return values are handled. However, the description lacks explanation of the `brief` parameter and behavior when no match found. Adequate for a simple tool but with clear gaps.

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%, so description must compensate. It mentions supported identifiers but does not explain how `work_id` accepts them nor does it address the `brief` parameter at all.

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?

Description clearly states the tool retrieves single work details and lists supported identifiers (W-id, DOI, arXiv ID/URL, title), distinguishing it from sibling `search_works` which returns multiple results.

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?

Implies usage for fetching a single work but does not explicitly state when to use alternatives like `search_works` or when not to use this tool. No exclusions or comparative guidance provided.

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