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

Annotations are minimal (readOnlyHint=false, destructiveHint=false). The description states it 'gera cobrança, mexe em dinheiro', indicating a mutation that creates charges, but does not disclose any side effects, required permissions, or what happens upon success/failure. More behavioral context is needed.

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 cluttered with a list of actions that do not apply to this specific tool, making it longer than necessary. The key information (flattened action) is useful but buried among irrelevant details.

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?

For a tool that handles financial transactions (charges), the description fails to specify required fields within the 'data' object, expected return values, or error conditions. With three parameters, no output schema, and high complexity, the description is severely incomplete.

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 input schema has 0% description coverage, so the description must add meaning. It only vaguely mentions that 'data' should contain 'token/oferta' for charge_offer, but does not explain the 'account' or 'payment_link_ucode' parameters. The parameter descriptions are insufficient for an agent to construct correct inputs.

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 lists five different actions (create, add_offer, add_plan, charge_offer, charge_value) but the tool name and the flattened action note indicate this tool is specifically for 'charge_offer'. This inconsistency misleads the agent about the tool's actual purpose, making it unclear what this tool does versus its siblings.

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?

No guidance is provided on when to use this tool versus the sibling tools (e.g., hotmart_payment_links_write_create, hotmart_payment_links_write_charge_value). The description lists other actions that are actually separate tools, but does not direct the agent to use those alternatives.

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