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

With no annotations, the description carries the entire behavioral burden. It doesn't disclose whether the sync is asynchronous or returns a job/run handle, whether it replaces or merges existing product knowledge, whether it requires prior WooCommerce configuration, or what permissions/rate limits apply. Only the destination ('knowledge base') is implied.

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?

One sentence, front-loaded with the action and ending with the target location; no filler. It's appropriately sized for what it says, though the terseness leaves real gaps rather than wasting words.

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?

This is a mutation/sync tool with no annotations, no output schema, and an unexplained required parameter. The description should at minimum clarify the bot_id role, whether the operation is async, and how sync status can be checked (e.g., get_knowledge_sync_status). None of that is present.

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% for the single parameter bot_id, and the description never mentions it. An agent gets no explanation of what bot_id identifies (which chatbot receives the synced catalog) or its format, so the description fails to compensate for the empty 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 ('Trigger a catalog sync') and a specific resource ('WooCommerce products into the chatbot's knowledge base'), which is far more informative than a bare name restatement. It doesn't explicitly contrast with configuration siblings (configure_woocommerce, get_woocommerce_store_status), so it falls short of full sibling differentiation.

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 only implies when to use it – whenever a catalog sync is desired. It never says when not to use it, what prerequisites exist (e.g., store must be configured via configure_woocommerce first), or how it relates to alternatives like add_chatbot_knowledge or sync_cloud_storage.

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