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

No annotations are provided, so the description carries the full burden. It states the operation is a list, which implies read-only, but doesn't explicitly disclose side-effect absence, permission requirements, or what happens when no routes exist. The simple nature of list operations makes this acceptable, but more detail would improve transparency.

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 sentence with no filler, front-loaded with the verb and object, and ends with a useful cross-reference to the add tool. Every word earns its place.

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 list tool with one well-documented parameter and no output schema, the description sufficiently conveys what the tool does and its scope. It doesn't describe the return format in detail, but 'List' implies an array of routes, which is sufficient for an agent to call it correctly. Minor gaps around error cases and route structure keep it from a 5.

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 already fully describes the only parameter udid as 'iOS device UDID' (100% coverage). The description adds no additional meaning about the parameter, so it stays at the baseline 3 for schema-covered parameters.

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 ('List') and a specific resource ('mock/abort routes') with scope ('currently configured for this device'). It also names the companion tool ios_traffic_mock_add, which distinguishes it from the add operation. An agent can clearly tell this is the read-side counterpart to adding mocks.

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 implies usage (view current routes, likely after using ios_traffic_mock_add) but provides no explicit when-to-use versus alternatives like ios_traffic_mock_remove or ios_traffic_mock_status. It points to one sibling only, giving a hint but not full guidance.

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