Connect Store

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

Description discloses mutation behavior (connect creates, sync refreshes), return payload structure, and that credentials are never returned. Annotations are sparse (readOnlyHint=false, destructiveHint=false) and description adds value by detailing the sync process and security note.

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?

Three short, focused sentences: first introduces actions, second describes return payload, third notes credentials. No superfluous words, front-loaded with actionable information.

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?

Covers main actions and return format. Missing details on error handling, rate limits, or prerequisites (e.g., platform-specific requirements). OpenWorldHint suggests external API calls but not explicitly stated. Still mostly complete for a connection management tool.

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 covers 100% of parameters with descriptions. The description adds high-level context (return format, credential security) but does not significantly enhance parameter meaning beyond what the schema provides. Baseline 3 is appropriate.

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 the tool manages Shopify/WooCommerce connections with three specific actions (connect, sync, list), each with distinct purposes. It distinguishes from sibling tools which focus on other domains like customers, inventory, orders, etc.

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 explains when to use each action (connect for new store, sync for existing, list to show all). While it doesn't explicitly say when not to use or list alternatives, the context is clear given the tool's focused scope.

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