pve_metrics_server_delete

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

Discloses mutation nature, dry-run default, confirmation requirement, and side effects (stop forwarding, no data loss). Given no annotations, this covers key behavioral aspects well, though missing details on idempotency or error states.

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 concise sentences, front-loaded with 'MUTATION:' and verb. No superfluous words; every part earns its place.

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: action, dry-run, confirmation, and side effects. With output schema presumably handling return values, the description is mostly complete for a deletion tool, though could mention error handling or prerequisites.

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?

With only 33% schema coverage, description adds value for confirm parameter ('confirm=True to execute') but provides no additional context for metrics_id or proximo_target beyond schema titles. Partial compensation but insufficient given low coverage.

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 it deletes a PVE metrics server definition, with 'MUTATION:' prefix emphasizing the action. It distinguishes from related tools like pve_metrics_server_set and pve_metrics_server_list by specifying the delete operation.

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 clear context: dry-run by default with confirm=True to execute. Explains effect (metrics forwarding ceases, no data loss). However, does not explicitly state when to use vs alternatives or when not to use.

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