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

Goes well beyond the annotations by disclosing that the payment reduces the amount due, syncs to a connected accounting app (consistent with openWorldHint=true), that confirmation is on by default and configurable, and that a Cotlet API key with app access is required. This is meaningful mutation/auth context an agent would not otherwise have.

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 duplicates itself: 'Syncs to your accounting app if connected' is repeated verbatim in meaning by 'If your accounting app is connected, the payment syncs to it,' and the invoice-payment action is likewise stated twice. The opening also echoes the title, wasting the front-loaded position.

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 mutating, open-world payment tool with full parameter coverage and no output schema, the description covers the safety-relevant behavior (sync, confirmation, credentials) adequately. It stops short of nothing critical, though it omits what happens on sync failure or whether the payment is reversible.

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 invoice_id, amount, date, and method are already documented in the schema, including the cross-reference to list_invoices. The description adds no parameter-level detail (e.g., amount format, date handling), so the baseline 3 applies.

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 and resource: 'Record a payment received against an invoice and reduces the amount due.' An agent can identify the action. However, it offers no differentiation from the many sibling record_payment tools or from Tradify's own create_invoice, and it restates the same operation twice instead of clarifying scope.

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?

'By default you confirm each call; you can switch that off for this tool' and 'confirm with the user before each call' give operational context, but the description never says when to choose this tool over alternatives (e.g., other payment-recording siblings or manual invoice edits). Usage is implied, not explicitly routed.

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