List theme files

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

With no annotations provided, the description carries the burden of conveying behavior. 'List files in the local theme directory' clearly signals a read-only, non-mutating operation, and the filter examples illustrate accepted forms. It does not describe return format or recursion behavior, but for a simple listing tool this is adequate.

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 two sentences with no filler. The first sentence states the core operation and scope; the second provides practical filter examples. Every part earns its place, and the most important information is front-loaded.

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 tool with one optional parameter and no output schema or annotations, the description covers the key facts: what is listed, where, and how to filter. Minor gaps include the exact return format and the precise pattern syntax, but these are not critical given the tool's simplicity.

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 schema already describes the filter parameter at 100% coverage, giving a baseline of 3. The description adds value by showing concrete examples ('sections/', '.liquid', 'countdown') and using 'simple pattern,' which suggests broader matching than the schema's 'substring' wording. This goes beyond the structured 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 uses a specific verb and resource: 'List files in the local theme directory.' This clearly identifies the operation and distinguishes it from siblings like list_themes (lists themes) and search_files (searches file contents). The optional filter is described as a secondary behavior, not the core purpose.

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 intended use is implied: to list files, optionally filtered. However, the description does not explicitly state when to prefer list_files over related tools such as search_files, read_file, or theme_pull, nor does it mention when not to use this tool. Guidance is left to the agent's inference.

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