woo_products

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

No annotations provided, so the description must disclose behaviors. It only states the basic operation; no mention of authentication failures, rate limits, pagination, or that 'action' parameter controls list vs get. Minimal transparency.

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?

Single sentence is concise but omits essential information. Not well-structured to front-load key details beyond the basic operation.

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?

For a tool with 12 parameters, 3 required, no annotations, and no output schema, the description is extremely incomplete. No explanation of pagination, filtering (status, category, search), or expected return format.

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?

Description adds no parameter details beyond the schema. Schema description coverage is 50%; the description fails to compensate by explaining the 'action' and 'id' parameters, which are critical for usage.

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 or get WooCommerce products' clearly states the verb (list/get) and resource (WooCommerce products). It distinguishes from siblings like woo_customers or woo_orders, but does not explicitly differentiate from other product tools.

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 on when to use this tool versus alternatives (e.g., shopify_products). No mention of prerequisites or scenarios where listing vs getting is appropriate.

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