woo_scaffold_product_tab

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

No annotations are provided, so the description carries full burden. It states that admin tabs include fields and save logic, but does not disclose side effects (e.g., file generation), required permissions, reversibility, or output format. This leaves significant behavioral ambiguity for a scaffolding tool.

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, front-loaded sentence with no extraneous words. It efficiently communicates the core purpose and variants, earning 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?

With 6 parameters and no output schema, the description should clarify what the tool returns (e.g., file paths, confirmation) and any side effects. It only says 'generate a tab', which is vague for a scaffolding operation. The brevity leaves the agent under-informed about the full scope of the tool's action.

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% – all 6 parameters are described in the input schema. The description adds no additional meaning beyond grouping admin vs frontend location, which the schema already covers via the 'location' enum. Baseline of 3 is appropriate.

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 clearly states the tool generates a custom WooCommerce product data tab, specifying both admin (with fields and save logic) and frontend variants. This is a specific verb+resource combination that distinguishes it from the many other scaffolding sibling tools.

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 tool is for generating product tabs but does not explicitly state when to use it over sibling tools, nor does it provide guidance on choosing between admin/frontend or prerequisites. Usage is implied but lacks explicit alternatives or exclusions.

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