delete_static_route

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

Annotations already flag the operation as non-read-only and destructive, but the description adds the key behavioral fact that changes are staged in candidate config and only activate after commit. This is valuable context beyond the boolean annotations, though it does not mention error behavior or reversibility.

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 definition is a single front-loaded sentence with the [MODIFIES CONFIG] warning first, followed by the action and the critical staging note. Every part earns its place and there is 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?

For a three-parameter tool with no output schema, the description covers the critical workflow facts: what is deleted, where it is staged, and the need to commit. It does not describe expected results or failure modes when the route is absent, but the parameters are fully documented in the schema.

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 description coverage is 100%, so the schema already explains each parameter. The description's phrase 'from a virtual router' loosely echoes the virtual_router parameter but adds no new meaning beyond what the schema provides.

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 states a specific action ('Deletes') and resource ('a static route from a virtual router'), and the [MODIFIES CONFIG] tag sets expectations. This is clearly differentiated from sibling delete_* tools by the static-route resource and from add_static_route/get_static_routes by the delete verb.

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?

Usage is implied: use this tool when a static route needs to be removed. It does not explicitly say when to prefer this over add_static_route or get_static_routes, nor does it state exclusions such as requiring the firewall parameter in multi-firewall setups, leaving some selection inference to the agent.

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