network

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. It implies a read-only operation ('Dump') and specifies the data source, but it does not state whether the operation mutates anything, what the output format is, or any side effects or limitations. This is insufficient for a tool with no annotation support.

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, clear sentence with the key action and resource front-loaded. It is appropriately concise for a straightforward read tool, though given the tool's parameter complexity it could arguably be more detailed. Still, it earns its place without wasted words.

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 tool has 26 parameters, no output schema, and no annotations, yet the description provides only a one-line purpose. It lacks usage context, expected output, relationship to sibling tools, or any operational details. This is inadequate for such a complex tool.

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 high (88%), so the baseline is 3. The description does not add meaning beyond the schema; it only contextualizes the tool's purpose. The schema already provides descriptions for most parameters, but the description does not clarify how parameters like 'action' or 'include' map to this specific tool.

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 'Dump' with the resource 'recent HTTP(s) traffic parsed from the session app log', clearly distinguishing it from siblings like 'logs' or 'trace' which cover broader traffic or different log types. The source (session app log) and content type (HTTP(s)) are explicit.

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 guidance is provided on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description only states what the tool does, leaving the agent to infer usage context from the tool name and sibling set.

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