Delete subscription

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

The description says 'Remove' (mutation) but annotations set destructiveHint=false, which could be misleading. No additional behavioral context beyond annotations, such as permission requirements or side effects. IdempotentHint is set true, but the description does not reinforce this.

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 single sentence. No wasted words. However, it lacks detail that could be added without becoming verbose.

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?

Minimal context for a simple tool. Does not explain what happens after removal (e.g., subscription status, license). No output schema means the description could clarify return behavior. Adequate but with noticeable gaps.

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 has one 'node' parameter with 0% description coverage. The description does not explain what 'node' represents (e.g., node identifier). Fails to compensate for missing schema documentation.

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 'Remove the Proxmox subscription from a node' clearly states the verb (Remove), resource (Proxmox subscription), and scope (from a node). It distinguishes from sibling tools like set_node_subscription (add/update) and get_node_subscription (read).

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?

No guidance on when to use this tool versus alternatives. No mention of prerequisites or typical scenarios. The description does not indicate that get_node_subscription should be used to view current subscriptions, or set_node_subscription to modify.

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