Get WooCommerce Settings

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

The description complements the readOnlyHint annotation by explicitly stating it returns all setting IDs and their current values, and clarifies the 'checkout' => 'payments' alias. This adds useful behavioral context beyond the annotation without contradicting it.

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 concise sentences, front-loaded with the primary purpose, and every word adds value. It lists groups and return behavior without redundancy or wasted space.

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?

The description adequately covers the purpose, returns (all IDs and values), and valid group inputs, which is sufficient for this simple read-only tool. It does not address edge cases like empty results, but the output format is simple and the scope is well-defined.

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?

With 100% schema coverage, the schema already describes both parameters. The description adds value by enumerating the valid group values and noting the 'checkout' alias, which aids in selecting the correct 'group' parameter. It does not add new info for 'response_format' but schema covers it.

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 states a specific verb ('Read') and resource ('WooCommerce settings group'), lists the available groups, and distinguishes itself from sibling tools like wc_update_setting by focusing on read-only retrieval. It clearly conveys what the tool does.

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 provides clear context for when to use the tool (reading a settings group) and enumerates the groups it can access, effectively implying what it covers. However, it does not explicitly mention alternatives or when-not-to-use, though sibling tool names (e.g., wc_update_setting) make the distinction obvious.

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