Atualizar parcelas de um carnê

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, covering the core behavioral traits. The description adds that 'as cobranças das parcelas informadas serão modificadas', but this is already implied by the update verb. No extra insight on scope or reversibility beyond annotations.

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?

Two sentences, no redundant words. Front-loaded with purpose and usage. Every sentence serves a 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 is adequate for a batch update tool with high schema coverage and annotations. However, it lacks guidance on limits (e.g., max parcels), prerequisites (carnet must exist), and expected output/errors. The presence of an output schema partially compensates, but more context on coordination behavior would be beneficial.

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 100%, so the schema already documents all parameters (parcels array with parcel integer and expire_at string). The description does not add meaning beyond 'dados permitidos' and does not explain constraints or format of the fields.

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 updates multiple parcels of a carnet in a coordinated manner, using the verb 'Atualiza' and specifying the resource 'parcelas de um carnê'. It distinguishes from sibling tools like 'update_carnet_parcel' (singular) by highlighting the batch operation.

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 provides a clear use case ('aplicar revisões coordenadas a vários vencimentos') but does not explicitly state when not to use it or mention alternatives like update_carnet_parcel for single parcels. The sibling list implies the distinction, but direct exclusion is missing.

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