commerce_customer_profile

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

With no annotations, the description only partially covers behavioral traits by mentioning routing via the domain-agent dispatcher under authentication scopes. It fails to disclose whether the tool is read-only or destructive, which is critical for safe invocation.

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 and structured, with a clear purpose statement, routing context, and parameter list. No extra words, but the first line is slightly redundant.

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 has only 2 optional parameters and an output schema, the description is minimally complete. It covers the parameters and routing but lacks detail on the action's intended effect and output content.

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%, but the description adds meaning by explaining 'message' as a 'Free-text objective' and 'inputs' as 'Optional JSON string of structured inputs'. This compensates somewhat, though the explanations are brief.

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 that the tool runs the 'customer_profile' action via the domain agent dispatcher. It specifies a specific verb and resource, but does not elaborate on what the action does or how it differs from siblings like 'commerce_customer_360'.

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 is provided on when to use this tool versus alternative commerce tools. There is no mention of prerequisites, context, or when to avoid it.

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