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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false, so safety behavior is covered. The description adds little beyond that: it does not explain section-selection behavior, pagination, freshness semantics, or what the guide reference contains, and the sentence about sources is not actionable on its own.

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 short and front-loads the reader/router distinction, which is good. But the middle sentence is cryptic and the guide pointer is not self-explanatory, so the compactness comes partly at the cost of clarity.

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?

This is a complex tool with nested objects, enums, conditional section schemas, and 0% parameter description coverage; the description is far too thin to be complete. The output schema existing means return values need not be described, but the input behavior and section semantics still need much more explanation.

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 the description must carry parameter meaning. It gives a useful example covering entity, id, and species, but leaves sections, section_parameters, freshness, source_versions, and their nested objects entirely unexplained for an 8-parameter tool.

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 says it reads records/evidence sections and gives one example, which is more specific than the bare name 'get'. However, 'ordinary records/evidence sections' is vague and only distinguishes this tool from one sibling (variant_evidence); it does not clarify how it differs from search, resolve, or literature_search.

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 only explicit routing guidance is 'variants use variant_evidence', which is useful but narrow. There is no guidance on when to use this generic get versus search, resolve, or other siblings, and 'Sources constrain all lookups and identity dependencies' is too cryptic to function as usage guidance.

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