commerce_customer_segment

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds useful routing and scoping context that is not in the annotations, but it does not disclose what side effects may occur or what the action modifies, which is notable for a destructive-hinted tool.

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 compact and well-organized, with the core statement first followed by a clear Args list. Every line earns its place, though the description could have used a bit more room to convey the action's purpose without becoming verbose.

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 output schema exists, return values do not need explanation, but the description is still incomplete for practical use. An agent cannot tell what customer_segment does, what inputs are meaningful, or when this tool is appropriate, and the large sibling list increases the need for clearer contextual positioning.

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?

With schema description coverage at 0%, the description adds some meaning: message is 'Free-text objective' and inputs is 'Optional JSON string of structured inputs'. However, it does not explain what structured inputs are expected, provide examples, or clarify how message and inputs interact, so it only partially compensates for the schema gap.

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 a specific verb and resource ('Run the commerce domain agent action customer_segment') but does not explain what the customer_segment action actually does. It is clear that this is a dispatch wrapper, but the domain purpose remains vague and is not differentiated from similar siblings like commerce_customer_profile or product_customer_segment.

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 provides no guidance on when to use this tool versus alternatives. It mentions routing and scoping ('under your JWT, tenant, and company scope') but gives no context about which situations call for customer_segment or when a sibling would be more appropriate.

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