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

Annotations already declare readOnly, idempotent, and non-destructive, so the bar is lower. The description adds genuinely new behavior: pagination as the delivery mechanism, a termination condition, and the permission tier required — though the referenced 'next_offset' does not appear in the input schema, leaving the loop instruction partly unverifiable.

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?

Three short sentences, front-loaded with what the tool returns and how pagination works. Nothing is padded, though the mismatched 'next_offset' name wastes one of the few sentences on a non-existent parameter.

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 must carry the return-shape burden; 'paginated JSON' plus a next_offset instruction is thin and internally inconsistent with an integer `offset` input. It also leaves the enum breadth and the relationship to the sibling list tools unexplained, so an agent cannot confidently choose between them.

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 only 25% — only business_id is documented (by the schema itself). The description does not explain the eight `kind` values, the limit cap of 100, or the meaning of offset; instead it references 'next_offset', a field name that does not exist in the schema. It adds almost nothing beyond the structured data.

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: export records/audit history as paginated JSON. However, the stated scope ('business records and audit history') undersells the `kind` enum, which also covers client, billable, expense, timer, invoice, payment — and it never distinguishes itself from sibling list tools like invoices_list or expenses_list that surface the same resources.

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?

There is no guidance on when to choose this over the many *_list siblings, nor any prerequisite or exclusion. The only routing-adjacent statement is a permission note ('Viewers can read/export'), which is not usage guidance.

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