commerce_customer_360

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

The description only mentions routing through the dispatcher and scoping under JWT/tenant/company. It does not disclose any side effects, data modifications, or potential destructive behavior, despite annotations indicating destructiveHint=true and idempotent=false.

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 brief and to the point, with no redundant phrasing. However, its brevity comes at the cost of substance, so it is concise but not particularly informative.

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?

The description provides no context about the expected output, return schema, error conditions, or relationship to the customer_360 concept. It is a generic wrapper with no indication of what the underlying action accomplishes, making it incomplete for an agent deciding whether to invoke it.

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 minimal meaning to the two string parameters: 'message' as 'free-text objective' and 'inputs' as 'optional JSON string of structured inputs'. This is slightly more than the bare schema but still vague and does not clarify what kinds of objectives or structured inputs are expected.

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 says it 'runs the commerce domain agent action customer_360' but does not explain what customer_360 actually does. It is tautological and fails to distinguish this from the many other similarly generic domain-agent dispatcher tools in the sibling list.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, use cases, or conditions under which this dispatcher should be preferred over other domain actions or direct CRM tools.

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