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

Annotations already indicate readOnlyHint, idempotentHint, and no destructive behavior. The description adds that some actions require ucode, but does not disclose any additional behavioral traits such as pagination limits or authentication needs.

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 bullet formatting and the ambiguous '[Flattened action: plans]' note. It front-loads the main purpose but the listing of actions adds clutter without clear delineation.

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 multi-action nature and lack of output schema, the description is incomplete. It does not explain how to select an action, what each action returns, or how parameters interact. Sibling tools cover list and offers, but this tool's description creates confusion about coverage.

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%. The description partially explains max_results and page_token as filters for list, and ucode as required for offers/plans, but does not cover the 'account' parameter. The action selection mechanism is not parameterized, leaving ambiguity.

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, offers, plans) but the tool name and flattened action suggest it is specifically for plans. It does not clearly distinguish from sibling tools hotmart_products_list and hotmart_products_offers, leaving ambiguity about the tool's exact purpose.

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 alternatives. It mentions filters for list and ucode requirement for offers/plans but does not state exclusions or preferred contexts.

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