Delete Industry Subscription

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

Beyond the annotations (destructiveHint, idempotentHint, readOnlyHint), the description discloses that webhooks will stop, idempotent behavior returns already_absent=true, and reversibility is only via re-subscribing. It also asserts ownership requirements, adding context beyond the structured metadata.

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 and front-loaded with the core action. Each sentence adds value: purpose, side effect, idempotency, reversibility, and usage trigger. No redundant or filler content.

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 deletion tool with one parameter and an output schema, the description fully covers the behavioral contract: what happens, idempotency, reversibility, and ownership validation. It is complete without requiring the agent to infer missing context.

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?

The schema description for subscription_id already provides full coverage (100%), including source (from list_my_subscriptions) and ownership requirement. The description adds no new parameter meaning beyond what the schema states, so the baseline of 3 applies.

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 action: 'Delete one NACE industry-monitoring subscription by its id,' specifying the resource and scope. It distinguishes the tool from siblings like subscribe_nace and list_my_subscriptions by focusing on deletion and the consequence of stopping webhook delivery.

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 gives explicit when-to-use guidance: 'Call only when the user has asked to stop monitoring an industry.' It also instructs the agent to obtain the id from list_my_subscriptions, making the integration context clear.

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