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

Beyond the annotations (readOnlyHint=false), the description discloses the exact side effects: creating a transaction, incrementing confirmed_count, and auto-enabling the rule after a threshold (default 2). This adds meaningful behavioral context that annotations alone do not provide.

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 concise, with the key behavioral summary front-loaded in the first sentence, followed by clearly labeled Args and Returns sections. Every sentence earns its place without redundant fluff.

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 single-parameter mutation tool with no output schema, the description provides the required input semantics, the side effects to expect, and the return value ('Updated debt payment details'). The threshold behavior is also disclosed, so an agent has enough context to call it correctly.

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?

The schema provides only the parameter name and type with no description, so the description must compensate. The 'Args' section explains that debt_payment_id is 'ID of the pending DebtPayment record to confirm', adding the necessary semantic meaning for correct invocation.

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 names a specific verb ('Confirm') and resource ('pending debt payment match'), and spells out the main effect: creating the corresponding debt-account transaction. This clearly distinguishes it from sibling tools like reject_debt_payment_match and list_debt_payments.

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?

The description clearly states it is for confirming a pending debt payment match, giving the agent a clear triggering context. It does not explicitly mention alternatives or when not to use the tool, but the 'pending' qualifier provides enough guidance relative to sibling confirm/reject tools.

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