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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Do not sign or send a payment' warning is consistent with these. The description adds one genuinely new behavioral fact — the temporary suspension pending commercial-readiness review. But it never states what happens if the tool is invoked (error? no-op? empty response), leaving the operational behavior undisclosed.

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 tight sentences, all earning their place, with the suspension status front-loaded. 'Free previews remain available' and 'Do not sign or send a payment' are both actionable. The brevity is commendable, though it is achieved by omitting substance rather than by condensing it.

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 complex tool with 21 parameters, a nested object, and no output schema, the description covers only the suspension status. An agent cannot learn what the tool does, what it returns, or how the required parameters relate to the authorization workflow. The single 'free previews remain available' hint is the only gesture toward the broader context.

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?

With 21 parameters and only 19% schema description coverage, the description carries the burden of explaining parameter semantics, and it contains zero parameter information. There is no guidance on the required fields (supplier_company_number, invoice_number, invoice_date, amounts) or on the nested official_verification object. Nothing compensates for the massive schema coverage gap.

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 is a suspension notice, not a statement of function. It never says the tool authorizes Israeli invoice payments; it only references 'paid reports and x402 payments' in passing. An agent must infer the tool's purpose from its name alone, making this nearly as uninformative as a tautology.

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 gives explicit exclusion guidance ('Do not sign or send a payment') and directs agents toward free previews as a remaining path. However, it never names the specific alternative tools among the siblings (e.g., preview_israeli_invoice_payment_gate_free), and it offers no positive statement of when or how the paid tool should be used.

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