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

With no annotations, the description carries the full burden and does well: it frames the tool as a read-only report ('Report whether...'), lists the exact data returned, and even explains a behavioral nuance—a route that never matches shows mocked: 0. It does not explicitly state 'no side effects', but the reporting language makes the non-mutating nature clear.

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 two dense sentences with no filler. The core status fields are front-loaded, and the counter-confirmation tip earns its place by teaching the user how to interpret the output.

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 low-complexity status tool with a single parameter and no output schema, the description is complete: it explains what is reported, enumerates the counter categories, and provides concrete interpretation guidance. An agent has enough to invoke it correctly and interpret the result.

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 only parameter, udid, is already fully described in the input schema with 100% coverage. The description adds no additional parameter-level guidance, which is acceptable because the schema already provides the necessary meaning.

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 uses a specific verb ('Report') and names a concrete resource: Chrome/WebView interception state on the device, including page target, active routes, and hit counters. This clearly distinguishes it from mock management siblings like android_devtools_mock_add/mock_list/mock_remove, which configure rather than report status.

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 guidance to 'Check the counters to confirm a mock is actually firing' implies a clear diagnostic use case: verify that an armed mock is being hit. However, it does not explicitly state when to prefer this over android_devtools_mock_list or other status tools, nor does it name alternatives or exclusions.

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