create_theme

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

With no annotations present, the description carries the full burden for behavioral disclosure. It fails to mention any side effects, prerequisites, or post-conditions of creating a theme, such as whether the theme is published or how the source is processed.

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?

While the description is short (six words), it is under-specified rather than concise. The brevity comes at the expense of meaningful information, similar to the 'Process' example.

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?

The description provides minimal context for a create operation with three parameters and no output schema. It does not explain what happens after creation, whether the source must be a valid Shopify theme ZIP, or any return value.

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 already documents all three parameters with descriptions for name, role, and source. The tool description does not enhance the understanding of these parameters, so the schema's high coverage warrants a baseline score of 3.

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 'Create a new theme' essentially restates the tool name without additional context. It identifies the action and resource but does not specify what a theme entails or differentiate from related operations like update_theme or publish_theme.

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 when-to-use or alternative tool references are provided. The description is silent on when to choose create_theme over the many sibling theme tools such as update_theme or publish_theme.

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