network

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

Discloses two useful behaviors: traffic is parsed from the app log rather than captured live, and the operation times out after 90 seconds. However, with no annotations, it does not state whether the operation is read-only, what happens on timeout, or whether an existing session/lease is required.

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?

A single sentence with the action front-loaded and the timeout constraint appended; there is no filler or redundant restatement. The missing period between 'log' and 'Times' is a minor formatting slip, but the structure is otherwise efficient.

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?

An 18-parameter tool with no output schema and no annotations requires more behavioral and selection context than this. The description leaves device resolution, action semantics, include levels, and return shape almost entirely to the schema, which itself has undocumented enums.

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 83%, so most parameter documentation is already in the schema. The description adds no parameter-level meaning; notably, the action enum (dump/log) and include enum (summary/headers/body/all) lack explanations in the schema and are not clarified here.

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?

Identifies a specific action (dump), resource (HTTP(s) traffic), and source (session app log). It does not explicitly contrast with siblings like logs or trace, but the HTTP(s) traffic specificity narrows the purpose enough to be useful.

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?

No when-to-use guidance is provided, and no alternatives or exclusions are mentioned. The phrase 'from the session app log' implies context but does not explain prerequisites, session selection, or how this differs from sibling tools.

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