cigchat_set_integration_woocommerce

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

Without annotations, the description discloses the required 'Manage Team' scope and the HTTP endpoint, which adds meaningful context. However, it does not describe side effects, overwrite semantics, or confirmation behavior beyond the config update.

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?

One concise sentence that front-loads the action and includes the endpoint and auth requirement. No wasted words.

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 tool is simple with three self-descriptive parameters, and the description includes endpoint and scope. However, it lacks any mention of return value or success verification, which are not covered by an output schema.

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 input schema already provides descriptions for all three parameters (url, token, api_key) with an example, so the description adds no additional parameter semantics. Baseline of 3 applies due to 100% schema coverage.

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?

Clearly states 'Update the config of WooCommerce integration' with a specific verb and resource. The endpoint and sibling tools (get/clear) differentiate it from related operations.

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?

Does not explicitly state when to use this tool versus alternatives like get or clear integration, but the 'Update' verb implies its purpose for modifying existing config. No exclusions or alternative conditions are provided.

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