pending_web_orders

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

No annotations are present, so the description carries the burden; it explicitly states 'Read-only' and defines the exact row scope. It does not mention pagination or return shape, but for a zero-parameter read-only listing these are minor gaps.

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?

Two short clauses with the core meaning front-loaded; 'Read-only' is a valuable safety signal placed at the end. No wasted words.

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 simple zero-parameter list, the description gives source, payment status, fulfillment state, and read-only semantics. It could mention whether the result is paginated or all rows, but the tool is low complexity and no output schema exists to require more.

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 description has nothing to add. The baseline of 4 applies because no parameters require explanation.

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 identifies the resource: paid WooCommerce web orders awaiting fulfillment, explicitly scoped to the source='woo' rows of the Pending Order page. It lacks a strong verb like 'list' or 'get,' but the meaning is unambiguous and distinguishes it from broader pending-order 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?

The source='woo' and Pending Order page phrasing gives clear context for when this tool applies. It does not explicitly name alternatives such as pending_orders or state when not to use it, so it stops short of full routing guidance.

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