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

The description adds idempotency-key retry behavior, optional auth attribution, wallet control prerequisites, and public access details. However, 'Reuse idempotency_key for retries' asserts idempotent retry semantics while the annotation idempotentHint=false declares non-idempotence, creating a direct contradiction.

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 description front-loads the core action and packs prerequisites into short clauses. 'Never required for participation' and 'Public; no authentication required' overlap somewhat on optional/public availability, but the text is generally tight.

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?

An output schema exists and annotations cover open-world/destructive status, so return values and safety profile need not be restated. The description covers auth, idempotency, and wallet prerequisites, but leaves several parameter meanings to the schema and contains the idempotency contradiction.

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 0%, so the description must carry parameter meaning. It explains idempotency_key retry semantics and payer_address requirements for wallet invoices, but does not explain amount, currency, provider, or the provider enum choices, leaving significant gaps.

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 'Create' and resource 'general support invoice', and the scope 'general support' distinguishes it from sibling funding tools like claim_crypto_funding. It does not explicitly name sibling alternatives, but the purpose is clear.

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?

Gives context that it is never required for participation, optional bearer auth attributes contribution, wallet invoices require payer_address and later proof of wallet control, and it is public with no auth required. It implies usage but does not explicitly say when to choose this over other funding-related siblings.

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