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

Annotations already mark this as destructive, non-read-only, open-world, and idempotent. The description adds crucial context beyond them: the write is real and live, the agent cannot retry a failed write itself, it must relay the actual Xero outcome or failure verbatim, and approval through Invio Settings remains equivalent.

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 front-loaded with the purpose and immediately follows with the critical approval and execution warnings before the outcome instructions. It is somewhat verbose and repeats consent cautions already present in the schema, but the length is defensible for a destructive live-ledger write.

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 high-stakes destructive mutation with no output schema, the description covers approval preconditions, the need to inspect the pending change first, execution behavior, failure handling, outcome reporting, and the equivalent Settings path. An agent has enough information to call it correctly and report results safely.

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 coverage is 100%, and both parameters are already fully documented in the schema, including confirm's const true requirement and pendingChangeId provenance. The description reinforces consent semantics and says to call with confirm: true, but it largely repeats what the schema already provides rather than adding new parameter meaning.

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: it approves an already-proposed pending change and immediately executes it. It enumerates the draft-creating tools it applies to and explicitly distinguishes itself as the one tool in the connector that writes to a live Xero ledger.

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 explicit when-to-use and when-not-to-use guidance: only after the user has clearly approved THIS specific change in their own words, never speculatively, and never without first showing them the change summary via list_pending_changes. It also covers hesitation and questions by telling the agent to wait.

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