WooCommerce MCP Server

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

No annotations are provided, so the description carries the full burden. 'List all webhooks' implies a read-only operation, but it doesn't disclose behavioral traits like pagination behavior (hinted by parameters), rate limits, authentication needs, or what 'all' entails (e.g., active vs. inactive). It adds minimal context beyond the basic action.

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 concise with a single sentence 'List all webhooks.' It is front-loaded and wastes no words, making it easy to parse. Every part earns its place by stating the core action clearly.

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 low complexity (a list operation with optional pagination parameters), an output schema exists (which handles return values), and no annotations, the description is minimally complete. It states what the tool does but lacks details on behavior, usage, or parameter context, leaving gaps for an agent to infer correctly.

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 no parameter semantics beyond the input schema, which has 0% description coverage. However, there are 0 required parameters, and the tool likely functions without inputs, so the baseline is high. The schema defines 'per_page' and 'page' with defaults, but the description doesn't explain their role, though this is acceptable given the low parameter burden.

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 'List all webhooks' clearly states the verb ('List') and resource ('webhooks'), making the purpose understandable. However, it lacks specificity about scope or filtering compared to sibling tools like 'get_webhook' (singular) or 'create_webhook', which could help differentiate it better. It's not tautological but remains somewhat vague.

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 alternatives. For example, it doesn't mention if this is for bulk retrieval versus specific lookups with 'get_webhook', or how it relates to 'create_webhook' or 'delete_webhook'. The description offers no context or exclusions, leaving usage entirely implicit.

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