woo_scaffold_block_integration

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

With no annotations, the description must fully disclose behavior. It only states 'Generate a ... class' without detailing side effects (e.g., file creation, overwriting), authorization requirements, or output specifics. This is insufficient for a generation 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 extremely concise: two sentences with no redundant words. It efficiently communicates the core functionality and usage context.

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 tool generates code but lacks details on output location, naming conventions, file structure, or return value. For a scaffolding tool without an output schema, this is a significant gap that hinders the agent from understanding the full impact.

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 adds no parameter-specific meaning beyond the schema. The schema descriptions are adequate (e.g., 'scriptData' explained), but the description fails to provide additional context.

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 action ('Generate'), the resource ('WooCommerce Blocks IntegrationInterface class'), and distinguishes it from sibling tools like 'woo_scaffold_cart_block_extension' and 'woo_scaffold_checkout_block' by specifying 'without scaffolding the full checkout/cart block extension'.

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 explicitly says 'Use when you need the PHP integration layer without scaffolding the full checkout/cart block extension', providing clear context for when to use the tool. It implicitly indicates when not to use it, but lacks explicit mention of prerequisites or alternative tools beyond the two obvious siblings.

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