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

With no annotations, the description carries the burden of explaining behavior. It does so by revealing the scoring methodology: 'Each corridor chains origin ports, chokepoints, and destination ports into a single lane scored by its weakest link (highest risk waypoint). Scores combine real-time port congestion data with active natural disaster proximity.' This is meaningful beyond the tool name, though it omits response format and update cadence.

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 front-loaded with the core purpose and then provides methodological and usage detail in compact sentences. It is slightly dense with the long corridor list, and it claims '10 major corridors' but names only 9, which is a minor structural/conciseness blemish. Overall, every sentence 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 parameterless tool without an output schema, the description gives substantial context: the list of corridors, the weakest-link scoring mechanism, the data sources, and the target users. The main gap is that it does not state the output format (e.g., scores, levels, rankings) or update frequency, and the '10 corridors' versus nine listed creates a small completeness gap.

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, and the schema coverage is 100% (vacuously). The description correctly adds context about the fixed set of corridors and the scoring logic, which is all that is needed. No parameter details are 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 opens with a specific verb and resource: 'Monitor risk levels across 10 major ocean freight trade corridors.' It names the exact corridors and clearly differentiates this tool from sibling tools like get_chokepoint_traffic or get_port_congestion_trends by focusing on corridor-level risk scoring.

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 user contexts: 'Used by logistics planners for route risk comparison, procurement teams for supply chain exposure assessment, and freight forwarders for disruption early warning.' However, it does not explicitly mention when not to use this tool or name alternative tools for different scenarios.

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