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

Annotations already declare readOnlyHint=true and idempotentHint=true, establishing the tool as safe and idempotent. The description adds behavioral context beyond annotations by noting bulk support via 'product_ids' and listing available filters. It does not cover rate limits or auth, but the core behavior is well-documented.

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 structured with bullet points, but includes details about actions not part of this tool (summary, purchases, transactions, switch_plan_plans). This extra information, while contextual, adds length and potential confusion. The '[Flattened action: list]' note helps, but the description could be more focused.

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 no output schema and 8 parameters, the description covers purpose and parameters well, but lacks information about the return format or pagination behavior beyond mentioning page_token and max_results. The tool's overall behavior is adequately described for a list operation, but the omission of output details leaves a gap.

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?

Despite 0% schema description coverage, the description thoroughly explains most parameters: it lists filters (product_id, subscriber_email, status with explicit enum values, max_results, page_token) and identifies product_ids for batched execution. It also clarifies that subscriber_code is not for list but for other actions. This 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 clearly states that the tool performs a list operation on Hotmart subscriptions, with explicit filters. However, it also lists other actions (summary, purchases, transactions, switch_plan_plans) that are not part of this tool, which could blur the focus. The '[Flattened action: list]' note clarifies, but the inclusion of unrelated actions is unnecessary.

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 guidance by listing alternative actions (summary, purchases, transactions, switch_plan_plans) and their requirements. Since sibling tools exist for these actions, it effectively tells the agent when to use this tool (for list) versus the others. It lacks explicit 'when not to use', but the context is clear.

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