commerce_service_catalog

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

With no annotations, the description must disclose behavioral traits. It mentions routing under JWT/tenant/company scope but does not clarify if the action is read-only, mutates data, or has other side effects.

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 well-structured with bullet-point args. However, the brevity sacrifices essential information, so it earns a 4 for conciseness but not a 5 due to missing content.

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 presence of a generic router tool with many related siblings, the description lacks context on what the service_catalog action does, what outputs to expect (despite having an output schema), and how it differs from other commerce tools.

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 meaning to the two parameters by describing 'message' as a free-text objective and 'inputs' as an optional JSON string. This goes beyond the schema's defaults, but the added detail is minimal.

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 it runs the 'service_catalog' domain agent action, but it does not explain what that action does. It focuses on routing mechanics rather than the tool's function, leaving the agent unclear on what task it accomplishes.

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 given on when to use this tool versus sibling tools like commerce_catalog_sync or other commerce actions. The description does not provide context for choosing this over alternatives.

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