Torch

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

The description adds information beyond annotations: it states the tool blocks during capture, is read-only (consistent with readOnlyHint), and returns top flows by bytes. No contradictions with annotations.

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 two sentences. However, repeating annotation info (readOnlyHint) is slightly redundant, though not wasteful.

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 explains blocking and return format, but lacks details like maximum duration enforcement, result structure (no output schema), or interaction with filters. Adequate but incomplete.

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 has 100% description coverage for all parameters, so the description does not add significant new meaning. The description's mention of 'duration' is already covered in the schema.

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 'Capture a real-time traffic snapshot on a router interface,' with specific verb and resource. It also specifies the output ('returns top flows by bytes'), which distinguishes it from sibling tools that list static data.

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 mentions blocking behavior and auto-retry, but does not provide explicit guidance on when to use this tool versus alternatives like list_* tools. The context is implied but not stated.

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