bexio Invoice Payments

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

Annotations set destructiveHint=true. The description reinforces this by stating that delete 'permanently deletes the payment — cannot be undone.' It also discloses required fields for create, adding context beyond annotations. No contradiction with annotations.

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?

Description is a single paragraph that front-loads the general requirement (invoice_id) and then enumerates each action with its specific parameters. Every sentence adds value; no fluff or repetition.

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?

Given the tool's complexity (6 params, nested objects, no output schema), the description covers all actions and their required/optional fields. It lacks detail on return formats (e.g., for list/get), but the schema fills in some of that. Overall, quite complete for a multi-action tool.

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 baseline is 3. The description adds value by grouping parameters per action and explaining required conditions (e.g., 'set either bank_account_id or payment_service_id (1 = PayPal, ...)'). This clarifies usage beyond the schema's individual descriptions.

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?

Description clearly states 'Manage payments recorded on a bexio invoice' and lists four specific actions (list, get, create, delete). This distinguishes it from sibling tools like bexio_banking_payments or bexio_invoices, making the purpose unambiguous.

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?

Description specifies that all actions require invoice_id and provides action-specific requirements (e.g., create requires value and either bank_account_id or payment_service_id with enumerated values). It does not explicitly mention when not to use this tool versus alternatives, but the context is clear enough.

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