Inspect HTTP traffic (Ktor + OkHttp/Retrofit, via logcat)

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

Annotations already indicate readonly and non-destructive behavior. The description adds valuable context: it parses Ktor and OkHttp formats, auto-detects format, requires active logging, and redacts sensitive headers. This goes beyond what annotations provide.

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 concise, with just three sentences. The first sentence states the main purpose, the second details supported formats, and the third covers prerequisites and data redaction. There is no unnecessary text.

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 tool with 7 parameters and no output schema, the description explains the core functionality, supported formats, prerequisites, and redaction behavior. It could be slightly more complete by mentioning that returned objects are NetworkCall structures, but the maxCalls parameter hint partially covers that.

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 input schema covers all 7 parameters with descriptions, achieving 100% coverage. The description itself does not elaborate on parameters beyond the schema, so the baseline score of 3 is appropriate per guidelines.

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 clearly states the tool returns recent HTTP request/response pairs from a running Android app. The verb 'returns' and the resource are explicit, and the tool is differentiated from siblings like devilge_get_logcat by specifying it parses and formats HTTP traffic from logcat.

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 provides implicit usage context by stating prerequisites (HTTP logger must be active with certain log levels) and mentions auto-detection of formats. However, it does not explicitly say when to use this tool versus alternatives like parsing raw logcat, nor does it clarify when not to use it.

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