set_txn_category

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

The description discloses an important behavior: setting category='Random' requires confirm_random=true and is discouraged. However, with no annotations, it doesn't cover other behavioral aspects such as permissions, reversibility, or side effects on existing categories, leaving the description only partially transparent.

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 two sentences: the first states the primary action and scope, the second adds a critical caveat about 'Random.' It is front-loaded, concise, and contains no unnecessary words.

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 tool is a simple mutation with 4 parameters, but the description fails to explain the 'subcategory' parameter or return behavior. It covers the main action and an edge case, but gaps remain, making it adequate but not fully complete.

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 description adds meaning for txn_id (the transaction identifier), category (specifically calling out 'Random'), and confirm_random (required for Random), but it omits any explanation of 'subcategory.' With 0% schema description coverage, the description carries the burden and is incomplete for one parameter.

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 uses a specific verb ('Categorize') and resource ('transaction') identified by 'txn_id', and adds '(no rule)' to distinguish from rule-based categorization. It also differs from sibling 'set_merchant_category' by focusing on transactions rather than merchants.

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 states the tool handles a SINGLE transaction and provides clear context by discouraging 'Random' category, advising to 'pick a real category or leave it in the review queue.' While it doesn't explicitly name alternative tools, it implies when to use this tool vs leaving uncategorized.

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