hotmart_batch_subscriptions_cancel

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

No annotations, but description conveys destructive action (cancel). Lacks details on side effects like send_mail behavior or partial success handling, which would improve transparency.

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?

Two sentences, no redundant information, front-loaded with the main action.

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?

Sufficient for a simple batch cancel tool with output schema present. Missing info on error handling or send_mail impact, but not critical for basic use.

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 100%, but description adds value with an example format for subscriber_code (JSON array of strings). send_mail is not elaborated, but the schema provides a Portuguese description.

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?

Clear verb 'batch cancel subscriptions' with resource specified. Explicitly distinguishes from sibling 'hotmart_subscription_cancel' for single cancellations.

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?

States when to use (multiple subscriber_codes) and when not (single one), directing to the appropriate sibling tool.

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