Export ACF JSON via WP-CLI

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

The description adds a safety note that it does not execute arbitrary shell/PHP code, which is useful. However, it omits other behavioral traits such as file creation, overwriting, or permissions needed. With no annotations, the description carries the full burden and is insufficient.

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 very short (two sentences) with no wasted words. However, it is too minimal to be fully informative. It is concise but at the expense of completeness.

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 6 parameters, no output schema, and no annotations, the description should provide an overview of what the tool does and how parameters relate. It fails to do so, leaving the agent with insufficient context to invoke the tool correctly.

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?

There are 6 parameters with 0% schema description coverage, and the description provides no explanation of any parameter. It adds no meaning beyond the input schema, failing to compensate for the lack of schema descriptions.

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 'Run the whitelisted `wp acf json export` command', which indicates the action (export) and resource (ACF JSON). This differentiates it from sibling tools like acf_import_json and acf_sync_json, but does not explain what exactly is exported.

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 on when to use this tool vs alternatives (e.g., acf_export_json vs acf_list_field_groups). No mention of prerequisites, when not to use it, or context for the whitelisted command.

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