wordpress_list_files

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'List files' which implies a read-only operation, but does not specify permissions required, output format, pagination, error handling, or any constraints like file size limits or directory accessibility. This leaves significant gaps in understanding how the tool behaves beyond basic listing.

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, efficient sentence with zero waste, clearly front-loaded with the core action. It is appropriately sized for a simple listing tool, making it easy to parse quickly without unnecessary elaboration.

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 tool's moderate complexity (2 required parameters), no annotations, no output schema, and 0% schema coverage, the description is incomplete. It lacks details on behavior, parameter usage, and output expectations, making it inadequate for an agent to fully understand and invoke the tool correctly in context.

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%, so the schema provides no parameter details. The description mentions 'in a WordPress directory' but does not explain the 'path' parameter (e.g., format, allowed directories) or 'recursive' parameter (e.g., depth implications). It adds minimal value beyond the schema, failing to compensate for the low coverage.

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 'List files in a WordPress directory' clearly states the verb 'List' and resource 'files in a WordPress directory', making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'wordpress_file_info' or 'wordpress_read_file', which might handle individual file details, so it misses full sibling distinction.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools like 'wordpress_file_info' for file details or 'wordpress_list_theme_files' for specific directories, there is no indication of context, exclusions, or preferred scenarios for this general file listing tool.

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