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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds substantive context beyond that: signature and image bytes are never returned, and lite mode omits agreement text and event info, plus the underlying endpoints. It stops short of noting behavior for an unknown or missing 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?

The return payload is front-loaded in the first sentence, the mode switch follows, and the exclusion note comes last. Three tight sentences with no filler; the trailing endpoint paths are marginal but harmless.

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 in the structured data, the description takes on the burden of describing the return payload and does so field by field, including what is deliberately omitted. The only gap is error/not-found behavior and whether the waiver must belong to the caller's site.

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 coverage is 100%, with both waiver_id (including a UUID pattern) and lite fully documented in the schema. The description's lite explanation duplicates the schema text rather than adding format or edge-case detail, so the baseline 3 applies.

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 ("One signed waiver by id") and enumerates what is returned: signer, date signed, participants, form data, event, agreement text. That clearly separates it from the list/search/count siblings that return many waivers. It never names a sibling explicitly, so the differentiation is implied rather than stated.

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 main usage guidance is internal to the tool: "Set lite for only the collected form data" explains which mode to pick. There is no guidance on when to use this versus waiverfile_search_waivers or waiverfile_list_waivers, nor any prerequisite (e.g., needing a waiver id from a search first).

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