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

No annotations are provided, so the description carries the full behavioral burden. It clearly signals a read-only listing operation, discloses the role values and which role is live, and warns about draft/archived themes. This goes well beyond the bare schema information.

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 compact and front-loaded with the core purpose. The Routing line is slightly redundant because it repeats name/role/updatedAt already listed in the first sentence, though it does add the useful MAIN/live clarification.

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 one-parameter read tool with no output schema, the description covers what the agent needs: returned fields, the meaning of MAIN, and how updatedAt is used in a publish workflow. It could be stronger by explicitly naming the theme identifier in the output, but the core workflow guidance is solid.

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 only parameter, companyId, is already fully described in the schema with 100% coverage, including the membership requirement. The description adds no parameter-specific detail, but none is necessary because the schema already documents the sole parameter completely.

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?

States a specific verb and resource: 'List themes installed on the connected Shopify store.' It names the key returned fields (name, role, updatedAt), explains the role vocabulary (MAIN/UNPUBLISHED/DEVELOPMENT), and positions the tool as the pre-edit lookup for theme files, distinguishing it from file/asset editing siblings.

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?

Explicitly says when to use the tool: 'Use before reading or editing a theme file so you target the live theme, not a draft or archived one.' It also explains how updatedAt feeds into a later publish flow. It does not name the specific alternative sibling tools, but it gives clear contextual routing.

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