woo_validate_integration

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

No annotations provided; description lists validation checks but does not disclose whether tool is read-only, requires permissions, or has side effects. Behavioral traits beyond the checks themselves are not mentioned.

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?

Description is a single sentence that efficiently lists key validation checks. Slightly long but front-loaded with the main action.

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?

No output schema; description does not explain return value (e.g., boolean, detailed report). For a validation tool, missing output info reduces completeness despite listing checks.

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?

Single parameter 'path' already well-described in schema ('Absolute path to the plugin root'). Description adds no additional semantic value beyond what schema provides.

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?

Description clearly states it validates WooCommerce integration, listing specific aspects like HPOS compatibility, feature compatibility, hook usage, WC dependency, template safety. Distinct from sibling validation tools by targeting WooCommerce.

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?

Description implies usage for checking WooCommerce integration, but no explicit guidance on when to use vs other validation tools (e.g., validate_hook_usage) or when not to use.

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