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

Annotations correctly indicate read-only, idempotent, non-destructive. Description adds 'Flattened action: summary' (behavioral constraint not in annotations) and bulk support via product_ids. However, lacks details on authentication, rate limits, or response structure.

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 moderately concise but includes redundant listing of actions that may not all be active. The 'Flattened action' note is helpful but could be integrated more efficiently. It is not overly verbose but could be 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?

With 9 parameters, no output schema, and many sibling tools, the description is incomplete. It does not explain the return format, pagination beyond page_info, or how the summary action differs from the others. The description leaves significant gaps for an agent to use it correctly.

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 has 9 parameters with 0% description coverage. The description explains several filters (start_date, end_date, product_id, etc.) and mentions product_ids for bulk, adding partial meaning. But some parameters (account) remain unexplained, and the description does not fully compensate for the missing schema descriptions.

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 (history, summary, users, commissions, price_details) but the tool name and annotation suggest a summary-only function. It mentions 'Flattened action: summary', which implies only summary is active, creating confusion about the tool's actual purpose. It does not clearly distinguish from sibling tools like hotmart_sales_history.

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 the specific sales tools (e.g., hotmart_sales_history, hotmart_sales_commissions). The description merely states it's for reading sales, but does not provide context or exclusion criteria.

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