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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds nothing beyond that — no note on what a missing ID returns, no pagination or expansion behavior, no indication of the response payload.

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 very first sentence is duplicated verbatim and the operation ID hash is noise for an agent. What remains is a single useful clause, so the text is both redundant and under-informative.

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 (one nested query object) at 0% schema coverage, no output schema, and no annotations explaining return shape, the description provides nothing an agent needs to call the tool correctly. It falls far short of what a bare GET-by-ID tool requires.

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 description never explains the required 'id' path parameter or the free-form 'query' object. The only hint is the ':id' token embedded in the path string, leaving both parameters undocumented.

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 essentially the endpoint path repeated twice: 'GET /api/reassessments/:id' plus an operation ID. It implies a fetch of a reassessment by ID, but never states in words what the tool returns or how it differs from siblings like get_reassessments_pending or get_lease_reassessments.

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 guidance is a pointer that 'describe_operation provides native request schemas', which is a reference to a sibling tool rather than a when-to-use rule. There is no statement of when to pick this over the many other reassessment-related getters in the sibling list.

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