wordpress_wc_get_orders

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the tool 'gets' orders, implying a read-only operation, but doesn't clarify aspects like authentication needs, rate limits, pagination, or what 'filtering' involves (e.g., date ranges, statuses). This leaves significant gaps in understanding how the tool behaves in practice.

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, efficient sentence: 'Get WooCommerce orders with filtering'. It is front-loaded with the core action and resource, with no wasted words, making it highly concise and well-structured for quick comprehension.

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 complexity of retrieving orders (which likely involves filtering, pagination, and authentication) and the lack of annotations and output schema, the description is insufficient. It doesn't explain return values, error handling, or the scope of 'filtering', leaving the agent with inadequate information to use the tool effectively in a real-world context.

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 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description mentions 'with filtering', which hints at some parameterization, but doesn't detail what filters are available or how to use them. Since there are 0 parameters, the baseline is 4, but the description adds minimal value by implying filtering without specifics.

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 states the verb ('Get') and resource ('WooCommerce orders'), making the purpose specific and understandable. However, it doesn't distinguish this tool from potential siblings like 'wordpress_wc_get_products' or 'wordpress_wc_get_customers' beyond the resource type, which is why it doesn't reach a score of 5.

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 provides no guidance on when to use this tool versus alternatives. It mentions 'with filtering' but doesn't specify what filtering entails or when to choose this over other retrieval tools like 'wordpress_get_posts' or 'wordpress_search_posts'. Without any context or exclusions, it offers minimal usage direction.

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