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

Annotations already cover the read-only, non-destructive profile, so the description is free to add the things annotations cannot: it discloses that results are paged, that the payload is signer PII, and that the response is flattened into columns/rows. It stops short of stating any rate limits or response size ceiling beyond the schema's page_size cap.

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 core is a single dense sentence that front-loads the resource and range, followed by a short PII warning and the endpoint. Every clause carries information, though the parenthetical-heavy first sentence is harder to parse than it needs to be and could be split without loss.

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 paginated read export with no output schema, the description gives enough: row shape, optional column expansion, participant consolidation, and a PII caution. The only real gap is that it does not say whether a total count is returned alongside the page, which the page_index hint about 'the count' only obliquely implies.

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 genuine meaning by explaining the output shape each flag produces — custom form fields as extra columns, participants either comma-joined in one column or one row each. That connects consolidate_participants and include_custom_columns to the resulting table, which the parameter descriptions only do in isolation.

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 resource (flat waiver rows), its scope (a date range) and the exact shape of the returned data, plus the underlying endpoint GET /GetWaiverData. It is clearly a bulk-export counterpart to the per-waiver siblings, but it never names list_waivers or search_waivers, so differentiation is inferred from the 'export' framing 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 export-oriented framing ('the data behind the WaiverFile export', row-shaping flags) implies when this is the right tool, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative among waiverfile_list_waivers, waiverfile_search_waivers or waiverfile_find_waivers_by_reference. An agent must infer the routing from the sibling names alone.

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