shop_info

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

With no annotations, the description carries the burden. 'Returns' implies a read-only operation, and the listed fields give some context. However, it does not explicitly state that no modifications occur, nor does it mention any potential side effects, permissions, or return format details. For a simple zero-param tool, 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, well-structured sentence that front-loads the key action ('Returns basic information') and provides a useful list of example fields. No wasted 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?

For a simple, zero-parameter, read-only tool, the description is nearly complete. It lists the main fields returned, and the 'etc.' acknowledges there is more. Given the sibling context, it clearly differentiates from more specific shop-related tools. No output schema exists, but the description offers enough for an agent to understand the tool's scope.

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 schema requires no explanation. The baseline for zero-parameter tools is 4, and the description does not need to add parameter semantics beyond what the empty schema already conveys.

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 clearly states the tool returns basic Shopify shop information, listing specific fields (name, domain, email, plan, currency). The verb 'Returns' and resource 'basic information' are specific, and it distinguishes from more specialized sibling tools like shop_locales and shop_policies.

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 implies use when general shop information is needed, but it does not explicitly mention when to avoid this tool or point to alternatives like shop_locales or shop_policies. No clear exclusions are stated, so guidance is partially implied rather than explicit.

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