commerce_catalog_sync

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

The description does not disclose any side effects, data mutations, or destructive behavior beyond the annotation's destructiveHint. It fails to explain what happens when the action runs, such as whether it modifies catalog entries or triggers downstream processes.

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 extremely short but not informative. It wastes space on boilerplate about routing through a dispatcher without providing any concrete details about the action's purpose or execution.

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's apparent domain (commerce catalog sync) and the presence of many sibling tools, the description is severely incomplete. It lacks example usage, expected input format, output shape, or any indication of error conditions. An agent would be unable to invoke it effectively.

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 schema parameters (message and inputs) are completely undocumented. The description adds no meaning to the fields, leaving an agent to guess what a 'free-text objective' or 'JSON string of structured inputs' should contain for a catalog_sync operation.

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 a catalog_sync action but does not explain what that action does, why it exists, or how it differs from sibling tools. It is generic and relies entirely on the action name for meaning.

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, what message content or input structure is expected, or what alternatives might be more appropriate. The description offers no practical usage context.

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