delete_dhcp_static_mapping

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

With no annotations provided, the description must fully disclose behavioral traits. It indicates the destructive nature by stating 'Delete' and adds the confirm requirement, but does not mention that the operation is irreversible, what happens if the mapping_id does not exist, or any authentication requirements.

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, concise sentence that effectively communicates the core purpose and a key requirement without unnecessary words.

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 it is a delete operation with no annotations, the description is incomplete. It does not describe what the output schema contains, what happens on success or failure, or any prerequisites (e.g., existence of the mapping).

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 has 0% description coverage, so the description must compensate. It clarifies that 'mapping_id' is an identifier and that 'confirm' must be true. However, it does not explain the format of the ID or the purpose of confirm beyond 'requires'. This adds some value but not comprehensive context.

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 the action 'Delete' and the resource 'DHCP static mapping'. The specification 'by ID' and the requirement 'Requires confirm=true' differentiate it from sibling tools like add_dhcp_static_mapping and list_dhcp_static_mappings.

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 includes the necessary condition 'Requires confirm=true', which guides usage. However, it lacks information on when to use this tool over alternatives (e.g., other delete tools) or when not to use it (e.g., if the mapping is still in use).

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