Delete Price Subscription

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

Description adds context beyond annotations: 'permanently removes...and its event history.' Annotations already indicate destructiveHint=true, so this confirms and elaborates. Also notes API key requirement. No contradictions.

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?

Very concise: two main sentences plus a brief note about API key. Every sentence adds necessary information. Front-loaded with action and resource.

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?

For a simple delete tool with one parameter, the description covers action, side effects, prerequisite, and authentication requirement. Missing return value info but acceptable given no output schema and typical delete semantics.

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 describes the id parameter fully, but description adds value by specifying that the id comes from opa_list_subscriptions or opa_create_price_subscription, aiding correct parameter selection. Schema coverage is 100%.

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 ('delete'), specific resource ('price subscription', 'watch'), and distinguishes from sibling tools by mentioning id from opa_list_subscriptions.

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: 'when the user wants to stop/cancel/remove an ongoing watch.' Provides prerequisite to get the id. Does not explicitly mention alternatives or when not to use, but context is sufficiently clear for a focused tool.

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