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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and the description's 'Leitura' aligns. The description adds bulk support context, but does not clarify how actions are selected or what happens if multiple actions are implied. No contradictions.

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 lengthy and includes actions irrelevant to the tool's primary purpose (purchases). It could be significantly shortened by focusing on the flattened action and removing redundant action listings that belong to siblings.

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?

With 8 parameters, no output schema, and 0% schema descriptions, the description should provide more guidance on parameter combinations and return values. It only partially explains the purchases action but omits other parameters and does not address the tool's composite nature.

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 0%, meaning no individual parameter descriptions in the schema. The tool description partially compensates by mentioning subscriber_code requirement for purchases, product_ids for bulk, and filters for list. However, parameters like account remain undefined, and the mapping of actions to parameters is unclear.

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 multiple actions (list, summary, purchases, transactions, switch_plan_plans) that correspond to separate sibling tools. The 'flattened action: purchases' hint is buried and insufficient to clarify that this tool is specifically for retrieving purchase invoices. Thus, it fails to clearly distinguish from 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 explicit guidance on when to use this tool versus sibling tools like hotmart_subscriptions_list or hotmart_subscriptions_transactions. The description only mentions that purchases requires subscriber_code, but does not provide conditions or exclusions.

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