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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'Report' implies a read-only operation with no side effects, but it does not explicitly state that it does not modify the device or disclose any prerequisites (e.g., whether traffic monitoring must be active).

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 that front-loads the action and immediately enumerates the key output values. Every word is functional with no filler.

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 status tool, the description fully conveys what the agent needs to know to invoke it and interpret the result conceptually. It could mention return value structure or prerequisites, but the lack of an output schema and the simplicity of the tool make the description adequate.

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% and the single parameter 'serial' is documented as 'Android device serial (adb serial)'. The tool description adds no additional meaning about the parameter, so the baseline of 3 applies.

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 the specific verb 'Report' with a clear resource: TLS inspection status for an Android device. It names the concrete data points returned (whether TLS inspection is running, proxy mode, buffered flow count), which clearly distinguishes it from sibling tools like android_traffic_start/stop and android_traffic_flows.

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 this is the status-check tool within the android_traffic_* family, but it does not explicitly state when to prefer it over alternatives or mention any exclusions. An agent must infer from context that this is the read-only status counterpart to the start/stop/mock tools.

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