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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that it returns raw Hotmart data with pagination (items + page_info), providing useful behavioral context beyond annotations.

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 structured with actionable bullet points and includes a flattened action marker. It is informative but contains some redundancy (e.g., repeating tool name) and could be slightly tighter.

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 0 required parameters, no output schema, and existing annotations, the description covers actions, parameters, bulk support, and return format. It lacks output structure details but is adequate for a read tool.

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 compensates fully by listing 7 of 9 parameters with their formats (e.g., start_date/end_date YYYY-MM-DD, buyer_email, product_ids for bulk). Only 'account' is omitted, but the high coverage 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 it reads sales commissions via the Hotmart Payments API and lists specific actions. Although the name suggests a narrow focus, the list of multiple actions (history, summary, users, commissions, price_details) could blur the purpose relative to sibling tools like hotmart_sales_history. However, the flattened action note clarifies it's commissions focused.

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 mentions filters and bulk support but does not explicitly guide when to use this tool versus the many sibling sales tools (e.g., hotmart_sales_history, hotmart_sales_summary). The context is implied but lacks explicit alternatives or exclusions.

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