wp_woocommerce_get_settings

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

No annotations are provided, so the description carries the full burden. The verb 'Get' strongly implies a non-mutating read, but the description does not state what is returned, that omitting group returns all settings, or any access considerations. It is adequately clear but not behaviorally rich.

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 two short sentences: a front-loaded action statement followed by a compact enumeration of valid groups. There is no filler, repetition, or irrelevant detail.

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 one-parameter read tool with full schema coverage. The description plus input schema give the agent everything needed to select and invoke the tool correctly, including all valid group values and the optional nature of the parameter.

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%, so the baseline is 3. The description adds value by giving concrete examples of what each group contains, such as 'store address, currency' for general and 'guest checkout' for checkout. This helps an agent map a natural-language request to the correct group value.

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 opens with a specific verb and resource: 'Get WooCommerce settings by group.' It also enumerates the available groups, making the tool's purpose and scope immediately clear. This is easily distinguished from sibling tools like wp_woocommerce_update_settings or wp_woocommerce_status.

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?

The description makes the usage context clear: call this tool when you need to read WooCommerce settings, optionally scoped to a named group. It does not explicitly name alternatives or state when not to use it, but for a simple read-only settings tool this is a minor gap.

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