WooCommerce Produkt Details

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

No annotations are provided, so the description has full responsibility for behavioral disclosure. It only states that the tool 'retrieves details' without mentioning read-only nature, error handling (e.g., product not found), or response format. This is a clear gap.

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 a single sentence with no unnecessary words. It is concise and directly states the tool's function.

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 simple get-by-ID tool with one fully documented parameter, the description is minimally viable. However, without an output schema, it would benefit from saying what 'details' include or how the response is structured, so it is not fully complete.

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% because the only parameter, productId, is documented as 'Produkt-ID'. The description adds no extra meaning beyond that, so the baseline score 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 uses a specific verb ('Ruft ab' – retrieves) and clearly identifies the resource ('Details eines einzelnen Produkts' – details of a single product). The word 'einzelnen' distinguishes it from listing tools like woo_list_products, making the purpose unambiguous.

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 implies the usage context: use this tool when you need details of one specific product, as opposed to a list. It does not explicitly name alternatives or exclusion criteria, so it falls short of a 5.

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