gold_list_orders

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It adds meaningful context with 'BYOK fail-closed', indicating the tool fails closed if the user's key is missing or invalid, and the GET method implies a read-only operation. It could also mention pagination or response shape, but it discloses the most important failure behavior.

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 one tight, front-loaded sentence with no filler. 'Gold PRO $29' signals entitlement, 'GET /wp-json/wc/v3/orders' gives the exact contract, and 'BYOK fail-closed' adds behavioral warning. Every chunk earns its place.

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 7-parameter tool with no output schema and no annotations, the description is incomplete. It does not explain pagination defaults, date formats, return structure, or authentication setup. An agent can make a basic listing call but cannot reliably use advanced filters or interpret the response without external WooCommerce knowledge.

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?

Schema description coverage is 0%, so the description needed to explain the seven parameters, but none are described. 'after', 'before', 'search', 'customer', and 'per_page' receive no format or meaning beyond their names. The Woo endpoint provides weak implicit context, but not enough to correctly construct filter values.

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 names the exact operation ('list Woo orders'), HTTP method (GET), and endpoint (/wp-json/wc/v3/orders), making it impossible to confuse with siblings like gold_get_order or gold_list_products. The action and resource are stated unambiguously.

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?

There is no explicit guidance on when to choose this tool over alternatives such as gold_get_order for a single order or gold_wc_batch for bulk operations. The word 'list' implies a list use case, but the description does not provide context, prerequisites, or exclusions.

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