commerce_trade_flow_lookup

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 mentions routing through the dispatcher and scope, which is standard platform behavior, but fails to disclose side effects, permissions, rate limits, or return format. For a tool likely performing a read or write operation, this is insufficient.

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 relatively short but includes unnecessary implementation details (e.g., 'Routes through the platform's domain-agent dispatcher under your JWT, tenant, and company scope') that are likely standard. It could be more concise but is not overly verbose.

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?

Despite having an output schema, the description does not mention return values or explain the concept of a 'trade flow'. The tool's purpose is not fully defined, leaving the agent with insufficient context to use it correctly.

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 0%, so the description must compensate. It states 'message: Free-text objective' and 'inputs: Optional JSON string of structured inputs', but does not explain what constitutes a valid objective or the expected structure for inputs. This adds minimal value beyond the schema's names and defaults.

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 states 'Run the commerce domain agent action trade_flow_lookup' but does not clarify what 'trade_flow_lookup' actually does. It is a vague verb+resource, and among siblings like commerce_tariff_lookup, the distinction is unclear. No specific output or behavior is described, so the purpose remains ambiguous.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention when to prefer trade_flow_lookup over commerce_tariff_lookup or other commerce tools. No exclusions or context for selection are provided.

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