remote_spy_dump

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states that the tool returns captured traffic, but does not disclose whether the operation is read-only, whether it flushes or clears the buffer, or any other side effects. 'Dump' suggests retrieval, but the lack of explicit safety information is a gap.

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, well-structured sentence that conveys the core behavior without any wasted words. It is front-loaded with the main action and is appropriately concise for the simplicity of the tool.

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 zero-parameter, no-output-schema tool, the description provides adequate information about what is returned. It lacks explicit details about the format of the traffic or dependencies on remote_spy_start, but given the tool's simplicity and sibling context, it is reasonably complete.

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 tool has zero parameters, which by the rubrics sets a baseline of 4. The empty schema confirms no parameter documentation is needed, and the description adds no conflicting information. Nothing further is required.

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 'Return the remote traffic captured since the spy started' clearly states a specific verb (return), resource (remote traffic), and temporal scope. It is not a tautology and distinguishes from sibling start/stop tools by focusing on retrieval.

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 explicit guidance on when to use this tool versus alternatives. The phrase 'since the spy started' weakly implies a prerequisite, but there is no mention of needing remote_spy_start first, nor any comparison to other siblings like get_by_path or remote_spy_stop.

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