hotmart_module_analytics_app

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

No annotations are provided, so the description must convey behavioral traits. It states the tool outputs a bar chart and data table, implying a read-only operation. However, it does not explicitly confirm it is read-only, mention authorization requirements, rate limits, or any side effects. For a tool with no annotations, the description could be more explicit about safety.

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 extremely concise: two short sentences that front-load the main purpose and output format. Every word adds value; there is no filler or redundancy.

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 tool has a single parameter, no output schema, and no annotations, the description adequately covers the core functionality: it explains what the tool does, the input needed, and the output format. However, it could mention if the data is aggregated or real-time, and it lacks any note about permissions or limitations relative to other analytics tools.

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?

The input schema has one parameter (subdomain) with description 'Members area subdomain.' The tool description adds no extra meaning beyond what the schema already provides, such as acceptable formats or examples. Since schema coverage is 100%, the baseline score is 3; the description does not elevate it.

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 clearly states the tool's purpose: 'Análise por módulo da área de membros — qty aulas por módulo.' It specifies the resource (modules), the metric (number of lessons), and the output format (bar chart + data table). This distinguishes it from sibling analytics tools like hotmart_churn_analyzer_app or hotmart_commissions_dashboard_app, which focus on other metrics.

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 provides explicit use cases: 'Use pra 'estrutura da área de membros', 'quantas aulas por módulo'.' However, it does not mention when not to use this tool or suggest alternatives among the many sibling tools, which would be helpful given the large number of analytics options.

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