commerce_dashboard_summary

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

No annotations are provided, and the description only notes that it routes through a domain-agent dispatcher. It does not disclose side effects, destructive behavior, rate limits, or any other behavioral traits. For a tool with no annotations, the description should bear more responsibility for transparency.

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 well-structured with a clear function statement followed by a routing note and parameter list. It avoids unnecessary fluff and is easy to parse.

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 the description explains the tool's action and parameters, it lacks detail about the output schema or what the dashboard summary returns. Given that an output schema exists but is not shown, the description should at least hint at the nature of the response (e.g., key metrics, format).

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 input schema has 0% description coverage, but the description adds meaningful explanations for both parameters: 'message' as free-text objective and 'inputs' as optional JSON string. This goes beyond the schema defaults and titles, significantly aiding the agent.

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 clearly states it runs a specific commerce domain action 'dashboard_summary' and distinguishes from sibling tools through its unique purpose. The tool name itself is descriptive, and the description reinforces that.

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 mentions routing under JWT, tenant, and company scope, providing context. However, it does not explicitly state when to use this tool versus alternatives (e.g., other commerce tools like commerce_revenue_by_channel), nor does it provide any 'when not to use' guidance.

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