get_global_trade_flows

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

No annotations are provided, so the description carries the full burden. It implies a read/query operation but does not state whether it is read-only, whether results are paginated, rate limits, data freshness, or what authentication is required. For a zero-annotation tool, this is a substantial 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?

Single efficient sentence front-loaded with the verb and resource, then enumerating returned data categories. No redundant phrasing, though it could be slightly tightened.

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?

No output schema and no annotations, so the description must compensate but doesn't. It does not explain the return structure, result volume, pagination, or behavior when filters are omitted, leaving significant gaps for a query tool with three optional parameters.

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 description coverage is 100%, with all three optional filter parameters clearly documented (mineral_type, origin_country, destination_country) including examples and the 'optional' nature. The description adds no parameter meaning beyond the schema, so baseline 3 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?

States a specific verb (Queries) and resource (global critical mineral physical trade corridor flows) with a concrete list of returned data categories. It is distinguishable from verification siblings, though it doesn't name or contrast any specific alternative.

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 siblings like optimize_mineral_trade_route or estimate_maritime_freight_and_carbon. A reader must infer context entirely from the description.

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