pve_metrics_server_delete

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

With no annotations, the description discloses mutation, dry-run default, confirm execution behavior, and outcome (status ok, null result). It also notes that config is re-creatable, which is helpful for the agent.

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, starting with a clear label ('MUTATION:'), then a one-sentence summary, followed by parameter behavior and consequences. No redundant or unnecessary 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?

Covers essential aspects: purpose, dry-run, execution, consequences. Output schema exists, so return details are not needed. Could mention prerequisites or permissions, but not required for a delete tool.

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 coverage is 100%. Description adds context about the confirm parameter's role in dry-run vs execution, which goes beyond schema descriptions. It also explains the result on confirm.

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 tool deletes a PVE metrics server definition, distinguishes dry-run vs execution, and specifies the result. It differentiates from siblings like pve_metrics_server_set.

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 explicit guidance on dry-run vs confirm execution, and consequences (ceases forwarding, no data loss, re-creatable). While it doesn't compare to alternatives, the sibling list makes it clear this is the delete counterpart to pve_metrics_server_set.

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