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

Annotations already cover read-only, idempotent, non-destructive behavior, lowering the burden. The description adds meaningful context by describing the result as 'bounded' and clarifying that it is for discovery/review rather than clinical use. It does not describe pagination or limits, but the output schema covers return structure and the annotations cover safety traits.

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 sentences with no filler. It front-loads the core action, states the scope, and adds a relevant boundary about appropriate use. Every sentence earns its place.

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?

For a read-only, idempotent retrieval tool with one required parameter and an existing output schema, the description is largely complete. It covers the purpose, scope, and appropriate-use boundary. The main gap is the absence of an explicit routing cue to sibling tools, but that gap is modest given the schema and annotations.

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 input schema provides 100% parameter coverage, including descriptions for work_id and from_work_id, so the description adds little new parameter-level meaning. It only reinforces that the tool centers on 'one Noodle work identifier,' which is already in the schema. Baseline 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 states a clear action ('Retrieve the bounded citation and semantic neighborhood') and a specific resource ('one Noodle work identifier'). It distinguishes the tool from detail/search siblings by focusing on neighborhood retrieval, though it does not explicitly name the distinction from get_publication_neighborhood.

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 gives useful context ('for literature discovery and professional review') and an exclusion ('not diagnosis or treatment'), so an agent can infer appropriate situations. However, it does not explicitly say when to use this tool versus get_publication_neighborhood, get_work_details, or search_biomedical_literature.

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