pbs_metrics_influxdb_http_delete

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

Covers risk (stored API token), immediate effect (metrics stop), dry-run vs confirm, return values ('{"status": "ok", "result": None}'), and synchronous execution. No annotations exist, but the description fully compensates. No contradiction with annotations.

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 a single, well-structured paragraph. It front-loads the purpose, then risk, then behavior, then alternatives, and ends with prerequisites. Every sentence adds value with no redundancy.

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's deletion nature with token concerns, the description covers all essential aspects: purpose, risk, dry-run, confirm, effect, return values, alternative, and prerequisite (PROXIMO_PBS_* config). Output schema exists, so return details are supplementary.

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 has 100% coverage, so baseline is 3. The description adds value by explaining confirm's role (dry-run vs execute), digest as optimistic lock, and the purpose of proximo_target. It goes beyond mere repetition of schema 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 starts with 'MUTATION: delete a PBS InfluxDB http metrics server configuration,' clearly stating the action and resource. It distinguishes itself from sibling tools (e.g., create, update, get, list) by specifically targeting deletion, and also notes it mirrors pbs_s3_client_delete.

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?

Explicitly states when to use (delete a config) and when not to (no UNDO primitive). Provides the alternative of re-creating with pbs_metrics_influxdb_http_create. Also explains the dry-run vs confirm behavior, giving clear guidance on safe execution.

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