categorize_bank_transaction_as_vendor_payment

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the agent knows it modifies data and may create entities. The description adds context about preferring matching over journals but does not detail what the tool actually does (e.g., creates a payment record, changes transaction status). For a tool with no output schema, more explicit behavioral description would be helpful.

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 four sentences, each serving a distinct purpose: stating the action, specifying usage context, and giving priority guidance. No fluff, front-loaded with the core purpose.

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?

The description adequately covers purpose, usage context, and guidance on alternatives. However, it does not mention the output or side effects (e.g., whether it returns a success indicator or the ID of the created payment). Given no output schema, a brief note on return value would improve completeness.

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?

All 12 parameters have descriptions in the input schema (100% coverage), so baseline is 3. The tool description adds no additional parameter-level meaning beyond what the schema already provides.

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 clearly states the tool categorizes an uncategorized bank transaction as a vendor payment. It distinguishes from siblings like categorize_bank_transaction_as_customer_payment and categorize_bank_transaction_as_expense by specifying 'payment of one or more vendor bills'.

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 explicitly advises when to use this tool ('when the bank line represents payment of one or more vendor bills') and provides a decision hierarchy: prefer matching, then this categorization, and manual journals as exception. This guides the agent away from alternatives.

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