woo_orders

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

With no annotations, the description should disclose side effects and operational constraints. It only states the actions without explaining that 'create' modifies data or any authentication requirements beyond schema fields.

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?

Extremely concise at 6 words, but overly terse for a complex tool with 12 parameters and 3 actions. Lacks structure; no separation of concerns.

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?

Severely incomplete given 12 parameters, nested objects (order), no output schema, and no annotations. Fails to explain return format, error handling, pagination, or creation requirements.

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 value beyond the input schema. Schema coverage is 50%, and parameters like store_url, consumer_key are unexplained. The action enum is defined in schema but not elaborated.

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 clearly states the tool works with WooCommerce orders and the three actions (list, get, create). It distinguishes WooCommerce orders from sibling tools like woo_customers by resource type, though no differentiation from order tools of other platforms.

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 like woo_products or shopify_orders. Missing recommendations for action selection or prerequisites.

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