commerce_plan_domain_intelligence

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 only says it runs a domain agent action and routes through a dispatcher. It does not disclose what the action does, whether it is destructive, requires permissions, or has other behavioral traits.

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 an Args section. It is efficient with no extraneous text, though it could be more informative without being longer.

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 no annotations, low schema coverage (0%), and output schema not used for description, the description is incomplete. It doesn't explain what the output represents, nor does it help the agent choose this tool among many siblings. It essentially just names the action.

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 0%, so the description must compensate. It names two parameters ('message' as free-text objective, 'inputs' as optional JSON string), adding basic meaning beyond the schema. However, the descriptions are minimal and lack format or constraints.

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 a specific domain agent action ('plan_domain_intelligence') and mentions routing through the dispatcher under scopes. This is clear but lacks specificity about what the action actually does, and doesn't differentiate it from sibling commerce tools like 'commerce_chat' or 'commerce_competitor_watchlist'.

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 notes that it routes through the dispatcher under certain scopes, but does not provide context or exclusions. With many commerce siblings, more guidance is needed.

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