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

The annotations already declare destructiveHint=true, so the agent knows this operation has destructive potential. The description adds useful context about automatic future generation and reliance on the Heartbeat system, but it does not clarify what the destructive aspect entails (e.g., whether charges are irreversible, what permissions are needed, or side effects on customer billing).

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 two sentences, front-loaded with the main action and scope, and every phrase adds value. No filler or repetition of schema field names. It is highly concise and well-structured.

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 the tool's complexity (scheduling, recurrence, 7 parameters, no output schema), the description adequately explains the core behavior but misses details like return value/confirmation, how to manage or cancel schedules, or edge cases. The Heartbeat mention is useful but does not fully compensate for the lack of output/behavioral detail.

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 all seven parameters already have meaningful descriptions in the schema. The tool description itself does not add additional parameter-level semantics beyond mentioning cron/recurrence, which is already captured by the 'recorrencia' enum. Baseline 3 is appropriate.

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 identifies the action ('Agenda uma cobrança') and the resource ('cobrança'), and distinguishes it from siblings like criar_cobranca by specifying future or recurring execution via cron/Heartbeat. This is a specific verb+resource+scope that immediately differentiates it from immediate charge creation tools.

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 states when to use it: for charges to be generated automatically in the future or on a recurring schedule. It does not explicitly exclude alternatives such as criar_cobranca for immediate charges, but the context is clear enough given sibling names. No explicit 'when not to use' is provided.

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