wordpress_wc_get_customers

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

Annotations are entirely absent, so the description must carry the full burden of behavioral disclosure. It only says 'Get' implying a read operation, but provides no details about pagination limits, return format, error behavior, or whether it retrieves all customers at once. No additional behavior is disclosed beyond what the name implies.

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 that is front-loaded and free of fluff. However, it is under-specified rather than efficiently detailed, so it earns a 4 rather than a 5.

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, no annotations, and an empty parameter schema, this tool is minimally described. The description fails to explain what 'Get' returns, whether all customers are listed, if any default ordering/limits apply, or what the response structure looks like. For a simple tool this might be acceptable, but the complete lack of context makes it insufficient.

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 is 4 per the rubric. The description adds no parameter meaning, but since there are no parameters, nothing is missing.

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 customers' uses a specific verb and resource, clearly distinguishing it from the sibling tool wordpress_get_users which retrieves WordPress users. It is direct and unambiguous, though it lacks any scope detail like 'list all' or 'get by ID'.

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. There is no mention of prerequisites (e.g., WooCommerce plugin active), filtering, or when to prefer this over wordpress_get_users. The description simply states the action with no contextual direction.

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