Set subscription key

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

Annotations already indicate destructive and write behavior. The description adds the explicit instruction to confirm with the user, which is valuable behavioral context. However, it does not elaborate on idempotency or other side effects.

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 extremely concise: one sentence plus a short warning. Every word adds value, and the risk warning is front-loaded for immediate attention.

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 high-risk, destructive operation, the description is too sparse. It does not explain the effect of setting the subscription key, the format of the key, or the necessity of the confirm parameter. Annotations and schema partially fill the gap, but the description should provide more 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 description provides no information about the parameters (node, key, confirm). With schema description coverage at 67%, the description should compensate but fails to do so, leaving the agent uninformed about required inputs.

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 identifies the action ('Set'), the resource ('Proxmox subscription key'), and the target ('on a node'). It distinguishes this tool from siblings like 'delete_node_subscription' and 'update_node_subscription'.

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 includes a risk warning ('HIGH RISK — ask the user to confirm'), but does not specify when to use this tool versus alternatives, such as when a subscription key already exists or when to use update_node_subscription instead.

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