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

The description adds important behavioral warnings: 'Irreversível em lote', max 200, and validation on empty/oversized result sets. However, annotations declare destructiveHint=false while the description calls the batch operation irreversible, which creates a safety-profile contradiction. Per the rubric, a contradiction with annotations forces a score of 1.

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 dense but efficient: every sentence carries actionable constraints, usage guidance, or alternatives. It is front-loaded with the core scope and limit, and the final bulk-support line adds needed specificity without padding.

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 20 parameters, no output schema, no required fields, and no parameter descriptions, this description is not complete enough for fully reliable invocation. It covers the high-level workflow and some error behavior, but it does not explain the meaning or accepted values of many parameters, nor what a successful response contains beyond the vague validation-error mention.

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 description coverage is 0% across 20 parameters, so the description must compensate. It adds useful rules: at least one filter and one update field, prefer new_category by name, and category_ids/account_ids/credit_card_ids enable batch execution. But most parameters, such as tag_action, paid_filter, description_find/replace, and new_tags, remain semantically undefined, leaving a substantial gap.

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 and resource ('Atualiza VÁRIAS transações por FILTRO de busca') and immediately states the max scope (200), making it clear this is a bulk update tool. It also distinguishes itself from line-by-line siblings by naming update_transactions_categories/descriptions.

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?

It explicitly tells the agent when to prefer this tool ('quando a mesma alteração vale para todas as linhas'), when not to use it, and which alternatives to use ('Para mapa linha-a-linha use update_transactions_categories/descriptions'). It also instructs pre-validation with list_transactions/search_transactions and defines minimum inputs ('ao menos um filtro e um campo a alterar').

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