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

The description indicates cancellation but does not disclose behavioral traits such as reversibility, side effects, or authorization needs. Annotations show destructiveHint=false, which may contradict the nature of cancellation, though not explicitly stated.

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 concise yet includes essential elements (action, bulk support). The structure is slightly fragmented but still efficient.

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's simplicity and lack of output schema, the description fails to cover return values, error handling, or prerequisites, leaving the agent with incomplete guidance.

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?

With 0% schema description coverage, the description must compensate. It explains subscription_id and subscription_ids for bulk, but omits account entirely. This adds partial value but leaves a gap.

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 cancels subscriptions, distinguishing it from sibling tools like kiwify_subscriptions_get and list. The verb 'cancel' and resource 'subscription' are explicit.

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 mentions single and bulk cancellation, providing clear context. However, it does not specify when not to use it or offer alternatives compared to similar write actions.

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