wafeq_simplified_invoices_tax_authority_report_create

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

Annotations already mark this as destructive and non-idempotent, but the description adds meaningful context beyond those hints: the action is irreversible, the document is submitted outside the organization, it cannot be recalled or undone through this API, and user confirmation plus content review are required before invoking. This is exactly the kind of behavioral disclosure an agent needs for a consequential external filing.

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 most important information—irreversibility, external filing, and the endpoint—is front-loaded in a compact first line. However, 'Report the simplified invoice to the tax authority for processing and validation' largely repeats the first line, so not every sentence earns its place. Overall length is still reasonable.

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?

The description fully covers what the operation does, where it submits the document, the irreversible consequences, and the required user-safety precautions. There is no output schema, but for a destructive external-filing action, the consequences and prerequisites matter more than return-value details, and those are thoroughly disclosed.

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?

The schema documents `idempotency_key` thoroughly, and the description's endpoint line ties the bare `id` parameter to a simplified-invoice document, adding meaning the schema's plain `string` type does not provide. With only 50% schema coverage, the description partially compensates for the undocumented `id`, though it could still be more explicit about required id semantics.

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 specific verbs like 'files' and 'Report' and names the exact resource: a simplified invoice being submitted to an external tax authority. It also includes the precise endpoint `POST /simplified-invoices/{id}/tax-authority/report/`, making it clearly distinguishable from sibling tax-authority report tools for regular invoices and credit notes.

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 indicates when to use the tool: to report a simplified invoice for external tax processing and validation. It also provides an important prerequisite—confirm with the user and check the document's contents before calling. It does not explicitly mention sibling alternatives or exclusions, so it falls just short of a 5.

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