commerce_tariff_lookup

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

With no annotations, the description must fully disclose behavior. It mentions routing through a dispatcher and scoping (JWT, tenant, company), but does not clarify whether this is a read-only lookup, side effects, permissions needed, or rate limits.

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 concise (three sentences) and front-loaded with the action name. The argument descriptions are separate, making it easy to scan.

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 lookup tool among many commerce siblings, the description fails to provide enough context for an agent to select it appropriately. The output schema exists, but the description does not highlight key aspects like typical use cases or relationship to other tools.

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 description adds minimal meaning to the two parameters: 'Free-text objective' and 'Optional JSON string of structured inputs.' While schema coverage is 0%, these descriptions are generic and could benefit from examples or constraints (e.g., what kind of inputs are valid).

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 it runs the 'tariff_lookup' domain agent action, which is essentially a tautology with the tool name. It does not explain what tariff lookup actually does (e.g., checking customs duties, rates, or regulations), leaving the agent to infer the purpose from the name alone.

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 over alternatives. Given the many sibling commerce_* tools, the description should specify scenarios (e.g., 'Use for looking up tariff rates for products') but provides none.

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