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

No annotations are provided, so the description must carry behavioral disclosure. 'Inspect' implies a read operation, but the description does not state required permissions, integration prerequisites, error behavior, or rate limits, leaving significant behavioral gaps for an unannotated 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 wasted words. It states the core purpose and the key data fields efficiently.

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?

For a simple one-parameter read tool, the description explains what status information is returned. However, it omits any explanation of the required bot_id parameter and provides no output-format context, which leaves a notable gap given the 0% schema coverage and absence of annotations.

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 description coverage is 0% and the only parameter, bot_id, is not mentioned in the description. The description adds no meaning about which bot identifier is required or what format it takes, so it fails to compensate for the undocumented schema.

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 names a specific verb ('Inspect') and resource ('WooCommerce integration status'), and it clarifies the included data ('synced products count, and sync freshness'). It is distinguishable from sibling tools like configure_woocommerce and sync_woocommerce_products, though it does not explicitly reference those alternatives.

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 provides no explicit when-to-use guidance, no exclusions, and no named alternatives. An agent can infer it is a read-only status check, but there is no instruction on when to choose it over sync_woocommerce_products or configure_woocommerce.

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