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

With no annotations, the description carries full burden and does substantial work: 'Snapshot' signals a read-only one-time view, 'DECRYPTED HTTPS' reveals coverage, 'captured since android_traffic_start' indicates a prerequisite session, and 'truncated' bodies are disclosed. It stops short of discussing failure modes or capture lifecycle, but the key non-obvious behaviors are stated.

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?

Four dense sentences with no filler; the core resource and dependency are front-loaded, and each sentence covers a distinct aspect (what it returns, body option, filters/limits).

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?

The description supplies return-field details (needed because no output schema exists), the prerequisite, and filtering options, while the required serial is documented in the schema. It is slightly brief about edge cases such as missing capture sessions, but is complete enough for normal use.

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; description adds some behavior around includeBodies ('also return headers + bodies') and describes filter effects, but largely restates schema details rather than adding substantially new parameter 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?

Description names a specific verb, resource, and scope: 'Snapshot recent DECRYPTED HTTPS flows (request/response) captured since android_traffic_start.' It also lists the principal fields returned, and the explicit dependency on android_traffic_start differentiates it from traffic mock/start/status and iOS counterparts.

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?

Clearly implies the tool is for reading traffic after android_traffic_start, and explains parameter use: includeBodies for bodies, urlSubstring/onlyErrors for filtering, limit for recency. It does not explicitly name when-not-to-use alternatives, but the context is strong and no other Android tool provides this exact view.

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