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

Discloses the side effect: automatically creates a Category Rule affecting future similar transactions. Also explains that it overrides automatic categorization and describes the batch return shape. No contradictions with annotations (readOnlyHint=false, etc.).

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?

Single paragraph with front-loaded main action. Contains all necessary details but is moderately dense (over 100 words). Every sentence adds value, though a slightly more structured format could improve readability.

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?

Given no output schema and minimal annotations, the description fully compensates: explains return shape, side effects, parameter sources, and batch error handling. Comprehensive for a batch update tool.

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?

Despite 0% schema description coverage, the description thoroughly explains the items parameter structure, including the required fields transaction_id and category_id, and directs the agent to sibling tools for obtaining valid IDs. Adds meaning far beyond the raw schema.

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?

Description starts with 'Corrects the category of one or more transactions (PATCH /transactions/:id)', using a specific verb and resource. It clearly distinguishes from sibling tools like openfinance_list_transactions and openfinance_list_categories by focusing on updating categories.

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?

Explicitly states when to use: 'use this to fix miscategorized transactions and improve categorization accuracy going forward'. Provides sources for IDs (openfinance_list_transactions, openfinance_list_categories). Lacks explicit when-not-to-use guidance but context strongly implies its purpose.

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