woo_orders

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

No annotations are provided, so the description must carry the behavioral burden. It names the actions but omits any behavioral traits like side effects (e.g., creation is destructive), required permissions, or pagination behavior for list. The description is too sparse for a tool with potentially destructive capabilities.

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 a single sentence that efficiently conveys the core purpose. It is front-loaded and concise, with no extraneous wording. However, it sacrifices completeness for brevity.

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 has 12 parameters, no annotations, and no output schema, the one-sentence description is insufficient. It fails to explain the three actions' conditions, response structure, or error handling. The description leaves the agent with significant gaps in understanding.

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 has 50% parameter descriptions, but the tool description adds no additional meaning beyond what is already in the schema. It does not explain parameter interdependencies (e.g., id required for get, order object for create) or format hints, which would help the agent use parameters correctly.

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 specifies three distinct actions (list, get, create) on WooCommerce orders, which is clear and action-oriented. However, it does not explicitly differentiate from sibling tools like woo_products or woo_customers, missing the top tier.

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 which action or any prerequisites or alternatives. The description merely states actions without context, leaving the agent to infer usage from parameter names.

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