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

Annotations already declare readOnlyHint=true, so safety is covered externally. The description adds the endpoint and the fields surfaced (severity, status, asset), but says nothing about result volume, pagination defaults, or whether filters are combinable — gaps that matter for an 8-parameter listing tool.

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?

Two tight sentences with the core purpose front-loaded, followed by a compact API reference. No filler, though a short note on filtering or paging would earn its place given the parameter count.

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 output schema the description is the only source of return-shape information, and it names just three fields; the rest of the deficiency payload is unexplained. Combined with no guidance on pagination behavior for a 2000-per-page endpoint, it is adequate but incomplete.

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 100%, so every parameter including enum-ish status and severity values is already documented. The description adds no parameter-level detail beyond what the schema provides, which is the expected baseline of 3.

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?

States a specific verb and resource ('List deficiencies') and defines the domain term with a parenthetical example (fire/life-safety defects) plus the API endpoint. It does not explicitly contrast with the sibling servicetrade_get_deficiency, though the list/get naming convention makes the distinction reasonably clear.

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 description implies a filtered listing operation and the schema exposes status/severity/company/asset filters, but there is no statement about when to use this tool instead of servicetrade_get_deficiency or how to page through results. Usage is inferable rather than stated.

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