get_chokepoint_traffic

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

With empty annotations, the description carries the full burden. It transparently states the tool monitors and returns data, listing output fields (vessel count, average speed, slow/stationary count, congestion score). It also adds the behavioral context of detecting rerouting signals. However, it does not explicitly mention whether the operation is read-only, but 'monitor' and 'returns' imply it. No side effects are suggested, and the real-time aspect is disclosed.

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 three sentences: the first states the core purpose and scope, the second lists the return fields, and the third provides the rationale. It is front-loaded with the key idea, contains no redundant words, and is well-structured.

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 tool with no parameters, no output schema, and no annotations, the description is quite complete. It names the specific chokepoints, lists the return metrics, and explains the signal it detects. It could add details about the time window or data units, but these are minor gaps for a real-time monitor.

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?

There are 0 parameters, so the baseline is 4. The description does not need to explain parameter semantics because there are none. It instead focuses on the tool's output and purpose, which is appropriate.

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 'monitor' and clearly identifies the resource: 'real-time vessel traffic and congestion at critical maritime chokepoints'. It lists concrete examples (Suez Canal, Panama Canal, etc.), which distinguishes it from sibling tools like 'port_congestion_monitor' that focus on ports. The return fields are also named, making the purpose unmistakable.

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 provides clear context for when to use the tool: 'When chokepoints congest or close, global shipping routes reroute within days — this data detects that signal in real time.' This implies a use case but does not explicitly contrast with alternatives or state when not to use it. It gives enough guidance without explicit exclusions.

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