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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses that nothing device-wide is changed, no certificate is installed, and the effect is scoped to the page. It also reveals match-order behavior, making side-effects and semantics transparent.

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 no filler. The core function and ordering are front-loaded, and the scope clarifications are packed into a second concise sentence. Every sentence 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 one-parameter list tool with no output schema, the description is complete. It explains scope, ordering, side-effect profile, and platform specificity. No critical information needed to call or interpret the tool is missing.

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 baseline is 3. The description adds no parameter-specific detail beyond the schema's 'Device id (Android serial or iOS UDID)', which is adequate for a single simple parameter.

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) on a specific resource (Safari/WKWebView mock/abort routes) and defines ordering semantics (match order, first match wins). It clearly distinguishes from sibling mock operations (add, clear, remove, status) and from other platforms' mock list tools by naming Safari/WKWebView exactly.

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 gives clear context: WEB CONTENT ONLY and explicitly states that native app code requests are not intercepted. This tells the agent when the tool applies, though it doesn't name an alternative tool for native traffic. The boundary is clear enough to avoid misuse.

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