commerce_campaign_brief

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

With no annotations, the description should fully disclose behavior. It mentions routing via a dispatcher but fails to specify if the action is read-only, destructive, or what side effects occur. The agent cannot assess risks or preconditions.

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 but somewhat structured with a one-liner followed by an args list. However, it is under-specified, and the argument descriptions are minimal. Could be more organized.

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 tool's complexity and many siblings, the description is incomplete. It does not explain what a campaign brief accomplishes, what the output looks like, or how it differs from similar tools. The agent lacks key context for selection.

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 explains 'message' as 'free-text objective' and 'inputs' as 'optional JSON string of structured inputs', but lacks details on formats, constraints, or examples, leaving interpretation vague.

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 'Run the commerce domain agent action campaign_brief' essentially restates the tool name without defining what a campaign brief is. It provides no insight into the tool's function or output, leaving the agent guessing.

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 the many other commerce tools (e.g., commerce_ab_test, commerce_assortment_gap_analysis). The routing details are generic and do not differentiate use cases.

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