subscriptions.cancel

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

No annotations provided, so description carries full burden. Fails to disclose whether cancellation is immediate/end-of-period, irreversible, triggers refunds, or requires specific permissions. Only implies mutation through the verb 'Cancel'.

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?

Single sentence is appropriately brief, but includes low-value implementation detail ('lifecycle endpoint') that doesn't help an AI agent understand when to select the tool.

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?

Insufficient for a destructive operation with undocumented parameters. Missing: parameter semantics (what is 'id'?), side effects (billing impact, immediate vs scheduled), and sibling differentiation. No output schema exists, but that doesn't excuse missing input documentation.

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% (id parameter undocumented). Description fails to compensate—it mentions 'Cancel a Ryft subscription' but doesn't specify that the 'id' parameter is the subscription identifier, nor its format constraints beyond minLength.

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?

States specific verb (Cancel) and resource (Ryft subscription) clearly. However, 'using the correct lifecycle endpoint' is implementation jargon that doesn't clarify purpose, and it doesn't distinguish when to use cancel versus update (e.g., termination vs modification).

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?

Provides no guidance on when to use this tool versus subscriptions.update, or prerequisites such as subscription status requirements. No alternatives or exclusions mentioned.

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