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

With no annotations provided, the description carries the full burden of disclosing behavior. The verb 'List' and phrase 'currently configured' imply a read-only operation that reflects the present state without modifications. However, it does not explicitly state safety traits (e.g., 'does not modify routes') or address potential side effects, permissions, or error conditions. This is adequate but not rich.

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, front-loaded sentence that begins with the verb 'List' and directly states the resource. It avoids redundancy and adds a useful cross-reference to android_traffic_mock_add for context. 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 parameter and no output schema, the description provides enough context to call it correctly: it names the resource, the scope (this device), and clarifies terminology via cross-reference. It doesn't mention return format or error cases, but these are less critical for a straightforward read-only list 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% for the single 'serial' parameter, and the schema already documents it as 'Android device serial (adb serial)'. The description adds no parameter-specific detail beyond the implicit 'for this device' mapping. Since the schema carries the full parameter meaning, a baseline 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 states a specific verb and resource: 'List the mock/abort routes currently configured for this device.' It clearly identifies the operation as a listing action within the android_traffic_mock family, distinguishing it from sibling tools like android_traffic_mock_add and android_traffic_mock_remove. The cross-reference to android_traffic_mock_add further clarifies what the routes are.

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 does not provide explicit guidance on when to use this tool versus alternatives. It only references android_traffic_mock_add for conceptual context, but does not state conditions like 'use this when you need to review current mocks' or contrast with add/remove tools. The absence of exclusions or alternative routing leaves the agent to infer usage from the name and sibling list.

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