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

The description adds context that the tool 'gera cobrança, mexe em dinheiro' (triggers charges, handles money), which goes beyond annotations by indicating financial impact. However, it does not disclose other behavioral details like idempotency, authorization requirements, or side effects.

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 not concise; it lists multiple actions that are not part of this tool, adding redundancy and potential confusion. It includes a disclaiming line about flattened action, but the extra list increases verbosity without added 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?

Given the complexity (3 params, no output schema, no required params), the description fails to explain the account parameter, data format, or return behavior. It does not compensate for the lack of annotations or output schema, leaving significant gaps for correct tool usage.

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?

With 0% schema description coverage, the description partly explains parameters: 'payment_link_ucode + data' for add_offer, but omits the 'account' parameter entirely and does not describe the structure of 'data'. The description lacks enough detail to guide parameter usage.

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 states the tool is for mutations on Hotmart payment links, specifically adding an offer, which is clear. However, it lists multiple actions in the description, which could cause confusion, but the flattened action 'add_offer' clarifies the specific action. It does not explicitly differentiate from sibling tools like add_plan.

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?

Usage is implied by naming and the phrase 'add_offer', but there is no explicit guidance on when to use this tool versus alternatives (e.g., add_plan, charge_offer). No when-not-to-use or alternative tools are mentioned.

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