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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds 'authoritative', indicating this is the source-of-truth record rather than a cached/derived view, but says nothing about response size, pagination, or error behavior for an invalid id.

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?

One compact sentence that front-loads the verb and the payload ('authoritative metadata and coverage') before the id constraint. No filler, though 'authoritative' carries a little marketing weight rather than operational detail.

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 an output schema present, return values need not be described, and annotations cover the safety profile; the description only needs to supply purpose and the id's provenance, which it does. The remaining gap is that 'coverage' is never defined, leaving the agent unsure what coverage means in the response.

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 single classification_id parameter is undocumented structurally. The description compensates partially by stating the id must come from list_classifications (provenance and expected form), but gives no format, length, or invalid-id semantics.

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?

Names a specific verb ('Get') and resource ('metadata and coverage' for a classification), and ties the id back to the sibling list_classifications, so the agent can place it in the workflow. It stops short of distinguishing itself from get_code_definition, which also fetches single-item definitions.

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?

'returned by list_classifications' makes the prerequisite and sequencing explicit: call list_classifications first, then fetch detail for one id. No when-not guidance or alternative tools (e.g., get_code_definition) are named, keeping it below a 5.

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