delete_subscription

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, and readOnlyHint=false. The description adds edition/license/permission constraints and route-specific 404/empty-list caveats that are not in the annotations, giving useful operational context beyond the structured fields.

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?

Two short sentences plus the endpoint are front-loaded with the action, followed by the key availability caveat. Every sentence adds value and there is no wasted text.

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 zero-parameter destructive endpoint with rich annotations, the description covers availability constraints and the route. It does not spell out irreversibility or side effects on related resources, but the destructive annotation already signals risk, so the remaining gap is minor.

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 tool has zero parameters, which sets the baseline at 4. The description adds no parameter detail, which is appropriate because the schema is empty and there are no parameter semantics to clarify.

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 the specific verb 'delete' and resource 'subscription', and the DELETE /subscription endpoint confirms the operation. An agent can distinguish it from get_subscription, refresh_subscription, and activate_subscription by the verb alone.

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 prerequisites such as Semaphore edition, license, and permissions, and warns that some Community routes return 404 or empty lists. However, it does not explicitly say when to use this versus the sibling subscription tools or when deletion is inappropriate, so usage is implied rather than directly guided.

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