delete_configuration_parameter

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether deletion is recoverable, whether parameters referenced by configurations can be removed, or what happens on a missing id. It does not contradict the 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?

A single front-loaded sentence with zero waste and no filler. It is structurally clean, though the brevity borders on under-specification rather than genuine conciseness.

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?

For a destructive mutation with no output schema, the description supplies no information about effects, failure modes, or recoverability; the destructive annotation is the only behavioral signal. An agent deciding whether to call a delete tool needs more than a restatement of its name.

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 a single parameter and 100% schema description coverage ("Configuration parameter UUID"), the schema already does the semantic work and the description adds nothing beyond it, which matches the baseline. The phrase "a configuration parameter" only loosely signals that id refers to an existing parameter.

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 names a concrete verb and resource ("Delete a configuration parameter"), which is more informative than the bare tool name and lets an agent match intent. However, it does not differentiate this from nearby siblings such as delete_configuration, purge_configuration, or restore_configuration, so the agent cannot tell which one applies to a given target.

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?

There is no guidance on when to use this tool versus delete_configuration or purge_configuration, no prerequisites, and no note that the parameter must exist first. The agent must infer usage purely from the tool name and the parameter's type.

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