Detach cash income from a holding

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

Annotations provide destructiveHint=true; description adds detail that it discards security transaction and returns bank credit to unmatched pool, and specifies that it only works on user-attributed rows (match_status 'matched'). No contradiction.

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?

Two sentences: first explains action and effect, second specifies usage and limitations. No extraneous words, front-loaded with key information.

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?

Covers all necessary aspects: purpose, prerequisites (user-attributed rows), error conditions, relationship with sibling tool, and intended workflow. No output schema needed for this tool type.

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% with descriptions. Description adds usage context for each parameter (e.g., cash_transaction_id must have match_status 'matched'), which helps beyond schema alone.

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?

Explicitly states verb 'detach' on resource 'cash transaction' and context of undoing an attribution. Differentiates from sibling tools like attribute_cash_transaction and unreconcile_cash_transaction by specifying its unique role.

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?

States when to use (wrong holding/details), when not to use (auto-matched feed rows), and provides follow-up action (detach then attribute_cash_transaction again). Includes explicit error condition for unattributed rows.

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