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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description usefully adds that authentication uses local WordPress credentials and no WooCommerce REST API keys are required, but says nothing about shape or size of the returned data.

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 sentences, front-loaded with the action and followed by the authentication note. No filler, though the second sentence is implementation trivia rather than agent-facing guidance.

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 tool whose whole purpose is returning some kind of "data indexes" and which has no output schema, the description should explain what comes back; it does not. An agent knows it is safe and how to authenticate, but not what it will receive or when this tool is the right pick among the specific wc_get_* siblings.

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 coverage is 100% and the single site_id parameter is fully documented in the schema, including the list_sites prerequisite. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 gives a verb and resource ("Retrieves WooCommerce store data indexes") but "data indexes" is vague — it never says whether this returns a list of available endpoints, store statistics, or resource collections. It cannot be confidently distinguished from specific siblings like wc_get_orders or wc_get_categories_report.

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 on when to use this tool instead of the many specific wc_get_* siblings, and no when-not-to-use condition. The only procedural hint (call list_sites first) lives in the schema, not the description.

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