Remove network routes

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

The description provides behavioral details about the effect on routes: removes one if pattern is given, all if not. This goes beyond the annotations which only indicate readOnly and destructive status. It does not mention side effects, but given the annotations, it is sufficient.

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 short and effective, using two clauses to convey the core functionality and parameter behavior 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?

For a simple tool with no output schema, the description covers the essential information: what it does and how the parameter affects behavior. It is complete in context.

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 parameter 'pattern' is described in the schema with the same information as the description. The tool description does not add additional insight beyond the schema, so the baseline of 3 is appropriate.

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: removing mocked routes. It specifies the behavior for both providing a pattern and omitting it, and the title 'Remove network routes' aligns. It differentiates from sibling tools like browser_route and browser_route_list.

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 when to use it: to remove a specific route or all routes. However, it does not explicitly mention alternatives or when not to use it, so it is adequate but not fully explicit.

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