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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description adds limited behavioral insight. It mentions bulk support (module_ids, user_ids) and the requirement for subdomain, which is useful but not extensive. No contradictions with 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 relatively short and uses bullet points for clarity. The 'Flattened action' note and bulk support mention are efficient. However, the phrasing 'Flattened action: modules' is somewhat cryptic and could be clearer.

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 8 parameters and no output schema, the description covers parameter usage for each action and bulk support. However, it lacks details on return values, does not clarify the relationship with sibling tools, and omits the 'account' parameter. Completeness is adequate but not thorough.

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 coverage is 0%, so the description must compensate. It maps parameters to actions (e.g., module_id for pages, user_id for lessons, is_extra for filtering) and notes bulk parameters. While not every parameter is explained (e.g., account is omitted), the description 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 the tool inventories course content and lists actions (modules, pages, students, lessons). However, it is unclear why multiple actions are in one tool when separate sibling tools exist (hotmart_club_lessons, hotmart_club_pages, hotmart_club_students). The phrase 'Flattened action: modules' suggests it primarily handles modules, but the inclusion of other actions blurs the 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?

The description specifies required parameters for each action (e.g., module_id for pages) but fails to guide when to use this tool versus sibling tools like hotmart_club_lessons. There is no explicit when-not or alternative guidance, leaving the agent to infer use cases.

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