hosting_checkIfWooCommerceIsInstalledV1

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

No annotations are provided, so the description must fully convey behavioral traits. It only says it checks for WooCommerce installation, but does not disclose the return format, side effects (read-only), authentication needs, or scope (all domains vs filtered). This leaves the agent with significant uncertainty.

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 wasted words. It is concise and front-loaded. However, it could be slightly more informative without exceeding efficient length.

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 simplicity of the tool (one optional parameter, no output schema), the description is incomplete. It does not specify the return value (e.g., boolean, list of installation details) or behavior when no domain is provided. This leaves gaps for the agent to infer.

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% for the single optional parameter 'domain,' which is already described as 'Filter by domain name (exact match).' The description adds minimal value by restating 'optionally filter by domain.' This meets the baseline but does not enrich parameter understanding.

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 verb 'Check' and the resource 'whether WooCommerce is installed on any WordPress installation of a domain.' It is specific and distinguishes from sibling tools like listInstalledWordPressPluginsV1 which list all plugins, not a specific check.

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 does not provide any guidance on when to use this tool vs alternatives, such as listInstalledWordPressPluginsV1 or searchWordPressPluginsV1. It only states what it does, with no when-not-to-use or comparison information.

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