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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the endpoint and the requirement for at least one reference id, but does not add much about return behavior, pagination, or matching semantics beyond that.

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 description is three short sentences with no filler. The purpose and the key parameter constraint are front-loaded, and the endpoint is a concise final 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?

For a read-only lookup tool with no output schema and full schema coverage, the description provides enough context to invoke it correctly, including the minimum requirement for selecting reference fields. It could be slightly richer about result shape or pagination, but the core invocation guidance is complete.

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%, so the baseline is 3, but the description adds meaning by explaining that reference_id_1/2/3 correspond to fields attached by an outside booking or reservation system and that reference_id_any matches across all three. This helps an agent choose between the specific and broad reference-id parameters.

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 states a specific verb and resource: finding waivers by reference ids attached by an outside booking or reservation system. It clearly distinguishes this from sibling list/search tools by focusing on external reference identifiers.

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?

It explains the key invocation condition: at least one of reference_id_1/2/3 must be supplied, or reference_id_any to search across all three fields. It gives useful context for when the tool applies, though it does not explicitly name or exclude sibling alternatives such as search_waivers.

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