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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds meaningful behavioral context beyond them: traffic is DECRYPTED HTTPS, bodies are truncated when includeBodies is set, and only the most recent `limit` flows are returned. It omits whether capture must be active (fails silently vs errors) and any retention window.

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?

Front-loaded with the core action and scope, then the returned fields, then the optional behaviors and filters. Four compact sentences with essentially no filler, though the field enumeration sits a bit dense.

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?

No output schema exists, so the description usefully enumerates the return shape (method, url, host, status, contentType, sizes, durationMs) and the body-truncation behavior. Combined with the 100%-covered input schema, an agent has what it needs, though pagination/retention semantics are only partially addressed via `limit`.

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 every parameter (limit, serial, onlyErrors, urlSubstring, includeBodies) is already documented in the schema. The description restates the includeBodies behavior and filters but adds little beyond what the schema provides, which is the expected baseline-3 case when the schema does the heavy lifting.

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 (snapshot decrypted HTTPS flows) and lists the fields each flow contains, making the tool's output concrete. It ties itself to the capture lifecycle via 'since android_traffic_start', which implicitly separates it from android_traffic_status and android_traffic_stop, but it never names a sibling or explicitly distinguishes itself from the mock tools.

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 phrase 'captured since android_traffic_start' implies the prerequisite that capture must be running, and the filter options hint at use cases (finding errors, matching URLs). However, there is no explicit when-to-use guidance, no statement of when to prefer android_traffic_status or the mock tools, and no mention of the iOS counterpart ios_traffic_flows.

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