Definir boleto do tipo balancete

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

Annotations already indicate destructive and non-readonly behavior. Description adds that it operates on a pre-existing charge and 'only organizes the provided data', clarifying it does not compute or validate beyond organization. No contradiction with 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: first states purpose, second gives usage context. No redundant words, well front-loaded. Every sentence adds value.

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?

Tool has output schema (not shown), so return values need no explanation. Description covers the action, precondition (charge exists), and result (produces billet with tabular content). Adequate for the complexity, but could mention that it modifies the existing charge.

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 coverage is 100%, so baseline is 3. Description does not explain individual parameters beyond implying the body contains tabular content. No additional semantics beyond schema definitions.

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?

Clearly states the tool defines a previously created charge to produce a balance sheet billet and informs its tabular content. The verb 'define' and resource 'cobrança' are specific, and it distinguishes from sibling tools like 'define_pay_method' by specifying the 'balancete' layout.

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 context: 'Use when the document needs this layout' and notes that Efí only organizes provided data. However, lacks explicit guidance on when not to use or alternatives among many sibling tools.

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