commerce_revenue_by_channel

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

With no annotations, the description bears full responsibility for behavioral disclosure. It mentions routing under JWT/tenant/company scope, but does not describe side effects, rate limits, or what actions the agent action performs beyond its name.

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 concise, front-loading the purpose. However, it repeats the tool name unnecessarily and could be more streamlined.

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?

While an output schema exists (so return values need not be explained), the description lacks details on what `revenue_by_channel` actually computes or expects, and does not differentiate from similar siblings. It meets the minimum but leaves gaps.

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 clear meaning to both parameters: `message` is a free-text objective, `inputs` is an optional JSON string. This is valuable given the input schema has 0% description coverage.

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 `revenue_by_channel`', which clearly identifies the tool's purpose. However, it does not differentiate it from sibling tools like `commerce_revenue_by_product` that serve similar purposes.

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?

The description implies usage for obtaining revenue data by channel, but provides no explicit guidance on when to use this tool versus alternatives like `commerce_revenue_by_product` or other commerce tools.

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