Export bePaid transactions

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral detail beyond that — it writes to a NEW file and notes that totals cover only successful payments — but omits auth requirements, where the file lands, and any size/rate limits.

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?

A single dense sentence that front-loads the action and output artifact before listing contents. No filler, though the second clause (contents list) could be trimmed without losing decision-relevant meaning.

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 7 parameters, no output schema, and a file-producing tool, the definition should at least say how the generated file is returned or where it is written. The 'totals cover successful payments' caveat is helpful, but the delivery mechanism of the export is left unstated.

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 71%, and the schema itself documents the date pattern, defaults, and enums. The description restates the output format options and hints at the period (from/to) and the successful-only total, but adds no syntax or semantic detail the schema lacks.

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 (writes/exports) plus the resource (all transactions of a period) and the concrete output artifact (new XLSX with summary + transactions sheets, or CSV). This clearly separates it from bepaid_list_transactions and bepaid_get_transaction, which return data rather than producing a file.

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?

Usage is only implied: an agent can infer this is for bulk period exports versus the list/get siblings, but the description never states when to choose it over bepaid_list_transactions or any exclusions (e.g. large ranges, unsupported filters). No explicit when/when-not guidance.

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