wordpress_file_info

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

With no annotations, the description carries the burden of behavioral disclosure. It does state the returned metadata fields, but it does not explicitly confirm it is a read-only operation, describe error behavior, or clarify whether 'path' refers to absolute server paths or WordPress media paths. The verb 'Get' implies non-mutating, but deeper context is absent.

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, concise sentence that is front-loaded with the action and resource. It contains zero redundant information and is appropriately brief for a simple metadata tool.

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?

Despite having only one parameter and no output schema, the description is incomplete: it does not define the path parameter, does not describe the return value structure, and offers no usage context. An agent would be unsure how to specify the path or interpret the result beyond the three listed fields.

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 coverage is 0% and the description does not explain the 'path' parameter. While the name is self-explanatory, the description fails to specify the expected format (absolute vs relative, file vs directory), which is essential for correct invocation.

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 the specific verb 'Get' with the resource 'file information' and lists the concrete data points (size, modified date, permissions). This clearly distinguishes it from sibling tools like wordpress_read_file (which reads file contents) and wordpress_list_files (which lists 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 such as wordpress_read_file or wordpress_list_files. There is no mention of prerequisites, path types, or exclusion criteria.

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