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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context by disclosing the authentication model: local WordPress auth with no WooCommerce REST API keys required. It does not cover behavior on a missing/invalid term ID, which keeps it short of a 5.

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 core operation front-loaded. The second sentence is relevant for auth planning, though the internal method reference ('Mirrors woocommerce-mcp-server method get_attribute_term') is somewhat implementation-facing for an agent's decision-making.

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?

This is a simple three-parameter read tool with full schema coverage, complete annotations, and no output schema, so little needs explaining. The description covers purpose and auth requirements; only the behavior for nonexistent IDs is unstated, which is a minor gap at this complexity.

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 description coverage is 100%, so each parameter is already documented, including the site_id guidance to call list_sites first. The description adds no meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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: 'Gets one term for a WooCommerce product attribute.' The singular 'one term' implicitly distinguishes it from the plural sibling wc_get_attribute_terms, but no sibling is named explicitly, so the differentiation is inferential rather than stated.

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?

Usage is only implied by the singular-resource framing and the required attributeId/termId. The description never states when to choose this over wc_get_attribute_terms or wc_get_product_attribute, nor does it give any exclusion or prerequisite guidance beyond the schema's site_id note.

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