wordpress_wc_get_top_sellers

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

No annotations exist, and the description discloses no behavioral traits. It does not explain what 'top selling' means (e.g., by quantity, revenue, period), nor does it mention sorting, limits, or any side effects.

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 of three words, extremely concise. Every word earns its place with no fluff.

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 lack of output schema, annotations, and parameters, the description is inadequate. It does not explain the return format, scope, or any constraints. For such a simple tool, additional context about the ranking metric would improve completeness.

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 schema coverage is 100%. Baseline for no parameters is 4; the description adds marginal value by identifying the resource as 'top selling products', but does not clarify the criteria for 'top selling'.

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 top selling products' clearly states the action (get) and resource (top selling products). It distinguishes itself from siblings like wordpress_wc_get_products or wordpress_wc_get_sales_report by specifying 'top selling'.

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 is provided on when to use this tool versus alternatives (e.g., get_products, get_sales_report). The description does not mention use cases, exclusions, or prerequisites.

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