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

With annotations only covering safety flags, the description carries real behavioral weight: per-device storage, live effect with no restart, mock-vs-abort outcome (canned response vs killed connection), and the certificate-pinning limitation. The 'update in place if id matches' semantics are consistent with idempotentHint=false.

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?

Dense and front-loaded, leading with the verb and the update-in-place caveat. Every clause carries information (prerequisite, live effect, pinning limit), though the multi-clause sentence is heavy and could be split for readability.

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 12-parameter mutation tool with no output schema, the description covers purpose, prerequisites, live behavior, and limitations well. The one gap is that it never says what is returned (e.g. the generated route id), which matters for follow-up calls to mock_list/mock_remove.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema for key parameters: it explains mode 'mock' vs 'abort' behavior and the id-driven update-in-place path. Other params (headers, delayMs, matchType) are left to 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?

States a specific verb+resource (add/update a mock or abort route) and precisely scopes it to the TLS-inspecting proxy on this device, distinguishing it from sibling tools like android_traffic_mock_list/remove and android_traffic_start. It even clarifies the update-in-place semantics when `id` matches.

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?

Gives a clear precondition (TLS capture must already be running via android_traffic_start) and an explicit exclusion (certificate-pinned apps can never be intercepted, so such routes never match). It does not name sibling alternatives (e.g. android_devtools_mock_add, webpage_mock_add) for the non-Android case, so it stops short of full when/when-not routing.

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