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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely useful operational context — local WordPress authentication with no WooCommerce REST API keys required — but says nothing about the shape or size of the returned data (e.g., whether it is a static code/name list).

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 with the action front-loaded. The reference to the upstream woocommerce-mcp-server method name is largely internal filler, but the authentication note in the same sentence 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 one-parameter read-only lookup with full schema coverage, the definition is serviceable but leaves the return value undocumented — there is no output schema, so the agent cannot know whether it gets a list of continent codes, names, or nested objects.

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 single parameter site_id has 100% schema description coverage, including the explicit instruction to call list_sites first and not to pass a URL or post ID. The description adds nothing about parameters, so the baseline 3 for fully documented schema 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?

States a specific verb and resource: 'Retrieves WooCommerce continents data.' The noun 'continents' is distinct from sibling resources like wc_get_countries and wc_get_currencies, so the agent can tell them apart by resource alone. It does not explicitly note the near-twin wc_get_countries, which keeps it from a 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?

There is no when-to-use or when-not-to-use guidance, and no mention of how this differs from wc_get_countries or wc_get_currencies, both of which sound closely related. The agent must infer that this is the right call whenever continent-level data is wanted.

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