Remove a URL user rule subscription

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavior: removal is irreversible locally, cached versions are destroyed alongside the subscription, and the source document/built-in rules are preserved. The recovery path via re-subscription is information the annotations cannot convey.

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 core action is front-loaded, followed by two short sentences scoping what is untouched and what is unrecoverable. No filler, though the phrasing 'a requested subscription' is slightly vague and could be tightened.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile. The description successfully rounds out the irreversible-delete semantics; only the undocumented parameters remain a gap.

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 description coverage is 0%, so the description carries the burden. 'Using its current revision' hints that expected_revision is an optimistic-concurrency guard, but neither parameter is named or explained in terms of format or failure behavior, leaving rule_id entirely unilluminated.

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 a specific verb (remove) plus resource (subscription) and scope (its cached versions), and explicitly bounds what is untouched (source document, built-in rules). It separates itself from the sibling family by clarifying it removes rather than edits or rolls back, though it never names the adjacent tools directly.

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?

Offers an implicit recovery route ('subscribe to its URL again to reconnect it'), which points at subscribe_user_rule, and warns that there is no local rollback. However it never explicitly states when to prefer this over rollback_user_rule or set_user_rule_enabled, so the routing guidance is only implied.

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