pbs_metrics_influxdb_udp_delete

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

Discloses mutation, dry-run default, synchronous execution, return value (null), and that it stops metrics forwarding. Explains risk level (LOW) and lack of undo. As annotations are absent, description fully carries the burden, covering all critical behavioral traits.

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 well-structured with clear sections (MUTATION, RISK_LOW, dry-run, execution, undo). Every sentence adds value and is front-loaded with purpose. Concise and efficiently informative.

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?

Given the tool has 4 parameters and an output schema, the description covers mutation nature, risk, dry-run behavior, execution details, return format, undo alternative, and config requirement. It is complete and context-rich, including cross-reference to PVE baseline.

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 input schema already provides comprehensive descriptions for all parameters (100% coverage). The description only reiterates the confirm parameter's dry-run behavior without adding new semantic meaning. Baseline score of 3 is appropriate.

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 explicitly states 'delete a PBS InfluxDB udp metrics server configuration,' with a clear verb and resource. It includes a MUTATION label, making the action unambiguous. It distinguishes from sibling CRUD tools through context.

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 when-to-use guidance: mentions dry-run default and that no undo exists, recommending re-creation with pbs_metrics_influxdb_udp_create. Also notes the PROXIMO_PBS_* config requirement. However, it does not explicitly state when not to use or alternative tools for checking existence.

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