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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds nothing beyond that: no mention of pagination, filtering behavior, result volume, or what the reclassification records contain, so it contributes no behavioral context of 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 body is one sentence duplicated verbatim, so half the text is pure waste. It is short, but brevity here reflects under-specification rather than disciplined editing.

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 two parameters at 0% schema coverage, nested objects, and no output schema, the description needed to explain the query parameter shape and the nature of the returned records. Instead it defers entirely to describe_operation, leaving the agent unable to construct a meaningful call from this definition alone.

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% and the schema shows a free-form 'query' object plus an empty 'params' object, giving the agent no guidance on accepted query keys. The description does not compensate at all; it only tells the agent to call describe_operation for schemas, which is a workaround rather than parameter 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?

The description is literally 'GET /api/cam/reclassifications' repeated twice, which restates the name and title rather than explaining what reclassifications are or what the response represents. An agent can infer it reads a CAM reclassification resource, but nothing distinguishes it from the dozens of sibling cam GET tools.

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 statement of when to use this versus alternatives, no prerequisites, and no exclusions. The only actionable guidance is a pointer to describe_operation for native request schemas, which is about schema discovery rather than tool selection.

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