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

Annotations already indicate read-only and idempotent. The description adds that it returns raw data with pagination (items + page_info) and supports bulk via product_ids. However, the inclusion of multiple actions that are likely not active (given '[Flattened action: history]') introduces confusion.

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 somewhat verbose with a bullet list of actions and technical notes. It is well-structured with a header and sections, but could be more concise without losing key 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?

No output schema and complex optional parameters. The description only vaguely explains the output as raw data with pagination. It fails to clarify the relationship to sibling tools or the exact meaning of the flattened action.

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 coverage, the description compensates by listing most parameters: start_date/end_date, product_id, transaction_status, buyer_email, max_results, page_token, product_ids. Only 'account' is not explained. This adds significant meaning beyond the schema.

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 'Leitura de vendas na Hotmart (Payments API)' and lists filters, indicating it retrieves sales history. However, it also lists multiple actions (summary, users, commissions, price_details) that correspond to separate sibling tools, creating ambiguity about the actual scope.

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 on when to use this tool versus sibling tools like hotmart_sales_summary or hotmart_sales_users. The description does not exclude other tools or specify context.

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