woo_scaffold_rest_extension

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

With no annotations, the description carries full burden for behavioral disclosure. It states the tool generates a controller but does not mention side effects like file creation, permissions, or any other behavioral implications. The description lacks detail beyond the primary action.

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 concise sentence that front-loads the key information. It could include more context without becoming verbose, but current length is appropriate and efficient.

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?

Given the tool is a code generator with 4 well-documented parameters and no output schema, the description provides adequate purpose but lacks details on what files are created or how the generated code integrates. It is minimally complete but could improve.

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 baseline is 3. The description does not add any additional meaning beyond the schema's own parameter descriptions. It does not elaborate on how parameters affect the generated code or provide examples.

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 it generates a WooCommerce REST API extension controller, specifying the action (generate) and the resource (extension controller under WC REST API). It distinguishes from sibling tools like scaffold_rest_module which are generic, and generate_controller which is not WooCommerce-specific.

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 usage for WooCommerce REST API extensions through its name and content, but does not explicitly state when to use this tool versus alternatives like scaffold_rest_module or generate_controller. No when-not or exclusion guidance is provided.

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