wordpress_list_files

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

With no annotations, the description carries full burden. It only states the core operation but does not disclose what the output contains (filenames, full paths, sizes), whether directories are included, how the recursive parameter behaves, or any path constraints. Read-only safety is implied by 'List' but not explicit.

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 sentence with no filler, front-loading the purpose. It is appropriately concise for a simple tool, though it omits essential parameter and behavior details.

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?

With no output schema and bare parameter schema, the description is the only documentation. It fails to specify return format, path interpretation, or recursive semantics, making it incomplete even for a straightforward list operation.

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 0%, and the description does not explain the 'path' or 'recursive' parameters. The agent is left guessing whether path is relative to the WordPress root, whether recursive defaults to false, and what the boolean controls.

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 'List files in a WordPress directory' with a specific verb (List) and resource (files in a WordPress directory). It distinguishes from content-reading tools like wordpress_read_file but does not explicitly differentiate from scoped siblings like wordpress_list_theme_files and wordpress_list_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 about when to use this tool versus alternatives. There is no mention of prerequisites, path limitations, or exclusions such as using list_theme_files for theme-specific browsing.

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