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

No annotations cover behavior, so the description carries the full burden and falls short. It does not explain what 'published' means for filtering, what happens if the specimen is unpublished or missing, or what the returned payload contains.

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?

A single short sentence is efficient and front-loaded, but here brevity comes at the cost of underspecification rather than economy of expression.

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 no annotations, no output schema, and 0% parameter coverage, the description should compensate heavily but does not. Key details such as the meaning of 'published', lookup semantics, and error behavior are absent.

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 lone parameter 'name' has 0% schema description coverage and the description adds no meaning to it. It is unclear whether 'name' is the specimen name, a UUID, or a free-text key, leaving the agent unable to construct a correct call.

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 has a verb (Return) and a resource (one published specimen), which is clearer than a tautology. However, 'specimen' and especially the qualifier 'published' are never defined, and nothing distinguishes this tool from siblings like carrier_record or coverage.

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 when-to-use guidance and no mention of alternatives among the sibling tools. An agent must infer that this is a single-record lookup by name, with no indication of when it is preferred over carrier_record or the docket variant.

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