get-shop-info

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

No annotations are present, so the description carries the full burden. The word 'Get' implies a read-only operation and the listed fields indicate what will be returned, but the description does not explicitly state that data is never modified or mention authentication/error behavior. For a simple getter this is adequate but not rich.

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 filler. The action, target resource, and key output fields are all front-loaded, and every word contributes meaningful 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?

For a parameterless getter, this definition is complete. It states the connected-store context and enumerates the returned fields, and no output schema is needed to understand these simple scalar values.

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?

The tool has zero parameters, so the baseline of 4 applies. The description's field list (name, domain, currency, plan) describes response content rather than parameters, which is appropriate since there is nothing for the caller to configure.

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 uses a specific verb ('Get') with a clear resource ('basic information about the connected Shopify store') and enumerates the exact fields returned (name, domain, currency, plan). This clearly distinguishes it from sibling resource-specific tools such as get-products and get-orders.

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 makes the context obvious: use it when store-level metadata such as currency or plan is needed. It does not explicitly list alternatives or exclusions, but no sibling tool appears to target store-level info, so the intended usage is clear enough.

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