find-unmanaged-traffic

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

With no annotations provided, the description carries the full behavioral burden. It does usefully define the domain logic ('unmanaged' = no app/env labels on sources or destinations), but it does not disclose output shape, whether results are aggregated, query cost/scale implications, or anything about the return format — significant given the absence of an output schema.

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?

Two sentences with zero filler: the first states the action and subject, the second defines the key term and its significance. The core function is front-loaded and every clause earns its place.

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 4-param tool with fully documented optional parameters and sensible defaults, the call contract is reasonably inferable. However, with no output schema, the description should explain what results look like (return format, ordering by 'top'), and it also lacks routing guidance relative to the traffic-related siblings — both are gaps an agent must resolve elsewhere.

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 100%, so the baseline is 3 and descriptors already document all four parameters. The description adds genuine meaning beyond the schema by defining 'unmanaged', which clarifies the central concept the direction parameter ('relative to managed workloads') depends on, adding value the schema alone does not provide.

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?

Description uses a specific verb+resource ('Find traffic involving unmanaged workloads or IP addresses') and defines the scope precisely: sources or destinations lacking app/env labels. The policy-blind-spot framing differentiates it semantically from sibling traffic tools like get-traffic-flows, though it never names a sibling explicitly.

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?

Usage context is implied by 'representing potential policy blind spots' — the agent can infer this is a discovery/analysis tool for surfacing coverage gaps. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as get-traffic-flows or detect-lateral-movement-paths that might overlap.

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