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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint. The description adds a meaningful extra guarantee: the response contains public data only and does not access private records. This is valuable privacy-related behavioral context beyond the annotations. No contradiction.

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 short, information-dense sentences. The first states what the tool does and its scope; the second clarifies access limitations. No filler or redundancy, and the key details are front-loaded.

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?

With only one parameter, 100% schema coverage, a full set of annotations, and an output schema present, the description covers the essential call-time knowledge. It does not need to explain return values or parameter syntax further.

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 already fully describes the id parameter with examples, so the baseline is 3. The description adds a small amount of value by reinforcing that the identifier is a stable connector identifier and by linking it to the operation's purpose.

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 uses a specific verb ('Fetches') and names a defined set of resources (biomarker, panel, document, comparison result) plus the key selection mechanism (stable connector identifier). This clearly separates it from search/list siblings, even if it does not explicitly name specialized getter alternatives.

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 the primary usage — retrieving a single public result when you already have a stable connector identifier — but it does not explicitly say when to prefer a specialized sibling such as get_biomarker or get_lab_package, nor does it list exclusions. The context is clear but routing guidance is left implicit.

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