wordpress_wc_get_orders

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. It does not state that this is a read-only operation, nor does it mention pagination, rate limits, or any other behavioral traits. The description is essentially a restatement of the tool name, providing no new insight.

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 concise sentence with no unnecessary words, making it easy to scan. However, it is under-specified, so while it earns points for brevity, it loses some for lacking substance.

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?

With no output schema and no annotations, the description is the only source of context. It fails to explain what the tool returns, how filtering works, or any operational details. For a tool that may be invoked by an AI agent, this is inadequate.

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 zero parameters, so the baseline for parameter semantics is 4. However, the description explicitly mentions 'with filtering', which implies filter parameters that do not exist in the schema. This contradiction is misleading and detracts from the parameter semantics.

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 'Get WooCommerce orders with filtering' clearly specifies the verb 'Get' and the resource 'WooCommerce orders', distinguishing it from sibling tools like wc_get_products or wc_get_customers. The mention of filtering hints at additional capability, making the purpose immediately understandable.

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?

The description offers no guidance on when to use this tool versus other getter tools, nor does it mention any prerequisites or alternative tools. It simply states the action without contextualizing its use case.

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