shopify_get_shop_info

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

The description lists the returned metadata but does not explicitly state that the operation is read-only or has no side effects. Since no annotations are provided, this is a minor gap, though the name implies a safe read operation.

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 14 words, front-loading the purpose ('Get shop-level metadata') and efficiently enumerating key fields.

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 provides a clear list of returned fields. It is self-contained for a simple info retrieval tool, though it could mention that the data is static and immediately available.

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?

There are no parameters, and the schema coverage is trivially 100%. The description adds value by listing the fields returned, which is useful context beyond 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 clearly states the verb 'Get' and the resource 'shop-level metadata', listing specific fields. It distinguishes well from sibling tools which focus on customers, orders, products, 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 implies usage for retrieving shop metadata but does not explicitly mention when not to use it or alternatives. However, the tool is unique among siblings, making the context clear.

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