commerce_pricing_landscape

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

No annotations are provided, so the description carries full burden. It mentions routing and auth scope but does not disclose critical traits like whether the tool is read-only, mutable, or what side effects occur. The output schema exists but is not described.

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 short and includes a parameter list, but brevity sacrifices clarity. It is structured but lacks substance for effective use.

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?

Given the lack of annotations, 0% schema coverage, and existence of sibling pricing tools, the description is severely incomplete. It does not explain what the tool does, making it nearly unusable for an agent.

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?

With 0% schema coverage, the description must explain parameters. It describes `message` as 'Free-text objective' and `inputs` as 'Optional JSON string of structured inputs', which adds minimal meaning. There is no detail on expected input structure or examples.

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 only says 'Run the commerce domain agent action `pricing_landscape`.' which is nearly tautological—it does not explain what the action does. It does not differentiate from sibling tools like commerce_price_optimization_run or commerce_pricing_intelligence.

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 alternatives. The description only covers routing details (JWT, tenant, company scope) but fails to specify appropriate contexts or exclusions.

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