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

Discloses a significant side effect: recategorizing automatically creates a Category Rule for future similar transactions. Also describes batch error handling (per-item errors do not fail the whole batch). This goes beyond the false annotations and gives valuable behavioral insight.

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 thorough but efficiently structured, starting with purpose, then input format, side effects, and response shape. Each sentence contributes unique information, though it is slightly dense.

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?

Despite having no output schema and only one nested parameter, the description covers the input format, source of IDs, side effects, and complete response structure. It is fully self-contained for an agent to use the tool 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 has no descriptions, but the description fully explains the 'items' parameter: an array of { transaction_id, category_id } with clear sourcing from list tools. This adds critical meaning beyond the structural 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?

The description clearly states the tool's function: 'Corrects the category of one or more transactions' with the HTTP endpoint. It uses a specific verb and resource, distinguishing it from sibling tools that list or fetch data.

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?

Provides explicit usage context: 'use this to fix miscategorized transactions and improve categorization accuracy going forward.' Also tells where to source transaction_id and category_id from sibling tools. It does not explicitly mention when not to use it, but the guidance is clear.

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