network_traceroute_stream

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

No annotations are provided. The description mentions streaming as SSE but does not disclose any behavioral traits such as rate limits, required permissions, or whether the stream is real-time. It refers users to describe_tool for more details, indicating incomplete disclosure.

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 very short (two sentences), but the first sentence 'Menu ID: traceroute' is unnecessary. It is concise but lacks structure and valuable content.

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?

Given 5 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain event format, usage context, or parameter effects, relying entirely on an external describe_tool call.

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 only 20%. The description does not explain any of the 5 parameters (target, maxHops, timeout, packetSize, worker_id). It adds no meaning beyond the schema itself.

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 that it streams traceroute hop events as Server-Sent Events. The verb 'stream' and resource 'traceroute hop events' are specific. However, it does not differentiate this from similar network tools like network_ping, but the name implies streaming.

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 on when to use this tool versus alternatives. The description only mentions using describe_tool for full guidance, which shifts the burden elsewhere.

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