wordpress_list_theme_files

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

The description omits important behavioral details, such as what happens if the theme does not exist, the impact of the 'recursive' parameter, and whether the tool is read-only. Since no annotations exist, the description fails to compensate.

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 extremely concise (one sentence, 8 words), front-loading the purpose. However, it sacrifices necessary details, making it less informative than it could be.

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?

Given the lack of annotations, output schema, and parameter documentation, the description is incomplete. It does not specify return value structure, error handling, or parameter formats, leaving significant ambiguity.

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?

With 0% schema description coverage, the description should explain the parameters ('theme' and 'recursive'), but it does not. It does not clarify expected values (e.g., theme slug or path) or the effect of 'recursive' (list subdirectories or not).

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 resource ('files in a theme directory'), distinguishing it from sibling tools like 'wordpress_list_files' (general files) and 'wordpress_list_plugin_files' (plugin files).

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 guidance is provided on when to use this tool versus alternatives (e.g., 'wordpress_list_files' for non-theme directories). No when-not-to-use or prerequisite information is given.

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