Pull theme

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It surfaces the non-obvious side effect of snapshotting the result in git and clarifies that pulling refreshes local files. It does not explicitly warn that local changes may be overwritten, but the 'before editing' guidance and download semantics make the main behavior transparent enough.

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 three concise sentences with no filler. The core action is front-loaded, followed by parameter routing and a clear usage directive. Every sentence earns its place and the total length is appropriate for the tool's complexity.

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 covers the core operation, git side effect, theme selection, and when to run it, which is sufficient for a tool with two optional parameters and no output schema. It could mention whether pulling overwrites local files or what the command returns, but the existing context makes correct invocation mostly unambiguous.

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?

Schema description coverage is 100%, so the schema already documents both parameters. The description adds marginal value by pointing out that theme_id comes from list_themes and confirming the omission behavior, but it does not elaborate on the 'only' glob parameter. This matches the baseline expectation when schema already covers parameter meaning.

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 states a specific action with verb and resource: it downloads a theme's files from Shopify into the local theme directory and snapshots the result in git. It clearly distinguishes from sibling theme_push by describing the opposite direction of data flow, so an agent can tell them apart without opening schemas.

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 gives explicit guidance on when to run the tool: 'Run this before starting an editing session so local files are fresh.' It also instructs how to choose the theme via theme_id from list_themes and explains the omit behavior for the live theme. It does not explicitly list when not to use it or compare to alternatives, but the timing and context are clear.

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