wafeq_invoices_tax_authority_report_create

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

The description strongly discloses that the action is IRREVERSIBLE, submits the document outside the organization, and cannot be recalled or undone through this API. This goes well beyond the annotations (destructiveHint=true, idempotentHint=false) by explaining the real-world consequence and adding a confirm-with-user directive.

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 warning is effectively front-loaded with the emoji and 'IRREVERSIBLE' label, but the phrase 'Report invoice to tax authority' is repeated in slightly different forms across the description, adding redundancy. It is still readable and scannable.

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 simple 2-parameter mutation tool with no output schema, the description covers the critical context: external submission, irreversibility, need for user confirmation, and the danger of the action. It does not discuss when to prefer this over sibling tools, but the resource-specific naming and endpoints make that a minor gap.

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 50%, with idempotency_key already well-documented in the schema. The description adds no explicit prose for the 'id' parameter, though the endpoint '/invoices/{id}/...' implies it is the invoice identifier. This is modest compensation but leaves the parameter semantics mostly to the schema.

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 uses a specific verb ('Report') and resource ('invoice'), and explicitly identifies the endpoint 'POST /invoices/{id}/tax-authority/report/'. The 'Invoices' marker distinguishes this from sibling tax-authority-report tools for credit notes and simplified invoices.

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 description clearly instructs to 'Confirm with the user before calling' and to check the document's contents first, which is essential guidance for an irreversible external action. It does not explicitly name sibling alternatives, but the resource scope ('Invoices') and endpoint make the selection obvious.

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