invoices_update_invoice_payment_methods_configuration

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

The description adds no behavioral context beyond what annotations already indicate. It fails to disclose what the update does, side effects, permission requirements, or effects on existing configuration. Worse, it misleads by referencing late fees, which is not supported by the schema. This is a serious failure in transparency.

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 is a single, concise sentence, but it is factually wrong regarding the tool's purpose. It does not earn its place because it misinforms rather than informs, making its brevity counterproductive.

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 is grossly incomplete. It fails to describe what the tool does, when to use it, or how to interpret the payment methods configuration. Given the nested object structure and the potential for confusion with sibling tools, the description is dangerously inadequate.

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 100%, so the schema already explains all parameters including paymentMethods and stripe. The description adds nothing and actively misleads by suggesting late fees, which is unrelated to the actual parameters. While the schema is clear, the description's contradiction undermines any value it might have had.

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 says 'Update template late fees configuration' but the tool name and input schema indicate this is about updating payment methods configuration (paymentMethods with stripe). The description directly contradicts the tool's stated purpose, making it misleading rather than clarifying. An agent would be unable to discern what the tool actually does from this description.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools like 'invoices_update_invoice_late_fees_configuration' and 'invoices_update_invoice_template_late_fees_configuration' exist, but the description provides no differentiation or conditions for selection. The misleading statement about late fees only adds confusion.

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