shopify_list_themes

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

The annotations already indicate readOnly and non-destructive behavior, lowering the bar. The description adds the meaning of the 'role' field (MAIN = live), which is useful, but it does not mention pagination, ordering, or any potential limitations on the result set.

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, information-dense sentence that front-loads the primary purpose and output format. It includes the crucial role interpretation without verbosity.

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 list operation with generic parameters, the description lacks essential context such as parameter semantics, filtering options, or relationship to other theme operations. While the purpose is clear, an agent would likely need additional information to use it correctly in a real scenario.

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 input schema has 0% description coverage, and the tool description does not explain any of the six parameters (project_id, project_ref, connector_account_ref, idempotency_key, effect, approval_ref). The description only mentions the output structure, offering no help on how to fill in the arguments.

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 action ('List') and the resource ('the shop's Online Store themes'), and it specifies the output shape with role semantics (MAIN = live theme). This distinguishes it from sibling tools like shopify_get_theme (single) or shopify_create_theme (write).

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?

No explicit guidance is given on when to prefer this tool over alternatives, such as shopify_get_theme for a single theme or other list operations. The description does not mention any filtering or selection criteria, leaving the agent to infer usage from the name.

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