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

No annotations are provided, so the description carries the burden. It discloses the destructive effect (removes routes) and the return value, but does not mention whether the operation is irreversible, whether confirmation is needed, or any side effects on active traffic mocking.

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?

Two sentences with clear front-loading of the main action and outcome. No filler or redundant phrasing.

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?

The operation is simple and the return value is stated. However, with no annotations or output schema, details about error conditions, idempotency, or interaction with active traffic mocking are missing. Still adequate for a basic remove operation.

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 documents all parameters adequately. The description rephrases the `id` and `all` behavior, adding slight clarity but not significant new meaning beyond the schema.

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?

Description clearly states the tool removes one mock/abort route by `id` or all routes when `all` is true, and returns the resulting route list. This distinguishes it from sibling tools like ios_traffic_mock_add and ios_traffic_mock_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 specifies the two removal modes (by id or all) and indicates the return value. It does not explicitly discuss when to use this versus alternative tools, but the context is clear from the resource name and sibling set.

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