pbs_metrics_influxdb_udp_update

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

Despite no annotations, the description discloses the mutation nature, risk level (RISK_LOW), dry-run behavior, confirm flag mechanics, synchronous execution, return format (null), and the absence of a snapshot primitive, providing comprehensive behavioral context.

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, front-loaded with 'MUTATION', and organized into clear paragraphs covering risk, workflow, and requirements without unnecessary verbosity.

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?

The description covers essential behaviors, risk, and config needs, and with an output schema present, return values are handled externally. A minor gap is lack of explicit precondition (e.g., server must exist) but this is implied by 'update'.

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 100% schema coverage, parameters are already documented. The description adds value by explaining the confirm parameter's role in the dry-run/execute workflow and the overall update process, which goes beyond static field descriptions.

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 updates a PBS InfluxDB UDP metrics server configuration, uses 'MUTATION' to indicate write operation, and distinguishes from sibling create/delete/get/list tools by the context of updating an existing server.

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 explains the dry-run/confirm workflow and mentions the requirement for PROXIMO_PBS_* config, but does not explicitly state when to use update instead of create or provide alternative tools for similar tasks.

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