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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the listed items are 'mock/abort routes' scoped to the current device, which is genuine extra context, but it says nothing about whether an active traffic session is required or what the returned route entries contain.

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?

One sentence, front-loaded with the verb and resource, with the sibling reference placed at the end as a secondary pointer. No filler words and nothing that needs trimming.

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 single-parameter read-only tool with full annotation coverage, the description is minimally sufficient but leaves gaps: there is no output schema, so the description could have sketched what a listed mock/abort route looks like or noted the need for an active traffic session. Adequate but not complete.

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?

There is a single parameter (udid) with 100% schema description coverage, so the schema already documents it fully. The description adds no syntax, format, or sourcing guidance for the UDID beyond the schema, so the baseline of 3 for high schema coverage applies.

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?

States a specific verb (List) and a specific resource (mock/abort routes configured for this device), and adds semantic detail beyond the name by clarifying these are mock/abort routes rather than general traffic. It cross-references the sibling ios_traffic_mock_add, but does not distinguish itself from ios_traffic_flows, ios_traffic_mock_remove, or ios_safari_mock_list-type siblings, so it falls short of full sibling differentiation.

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 parenthetical '(see ios_traffic_mock_add)' points at the sibling that creates these routes, implying the list/inspect use case, but there is no explicit when-to-use vs when-not, and no guidance relative to ios_traffic_status or ios_traffic_flows. Usage is implied rather than stated.

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