get-store-info

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

No annotations are provided, so the description carries full burden. It describes the tool as fetching 'live' data, implying real-time, and lists return fields. However, it does not explicitly state read-only behavior or mention side effects, which is a minor gap.

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?

Two sentences, zero wasted words. First sentence defines purpose and output, second provides actionable usage guidance. Perfectly front-loaded and efficient.

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 no output schema, the description lists key return fields and explains why to prefer channel name, which is sufficient for agent understanding. Lacks mention of error handling or behavior without required parameter, but context signals indicate no required params, so adequate.

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% with parameter descriptions. The description adds value by clarifying connectionId is a deprecated alias of salesChannelId and that salesChannelId starts with 'vc_', supplementing the 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 explicitly states the tool fetches live store info using a sales channel ID, lists specific return fields (channel display name, parent store name, currency, language), and clearly distinguishes itself from sibling tools like get-business-flows or get-code-example.

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?

Provides guidance on when to use ('to personalize the store being built') and how to interpret results ('prefer the channel name for user-facing text'), including context about multiple sales channels. No explicit when-not, but sufficient for a simple fetch tool.

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