Sync ACF Local JSON via WP-CLI

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

With no annotations, the description carries the full burden. It mentions dry-run support but does not disclose whether the sync is destructive, whether it overwrites database records, or any side effects. Missing crucial behavioral traits.

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?

Very concise (one sentence), but brevity comes at the cost of missing essential parameter explanations. Could be restructured to include a list or more context without being much longer.

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?

For a tool with 3 undocumented parameters and no output schema, the description is inadequate. It does not specify what happens on success, error cases, or return values, which an agent needs to handle syncing properly.

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%, so description must explain parameters. It only hints at dryRun via the 'dry-run' mention. The 'key' and 'type' parameters are not explained at all, leaving their meaning ambiguous.

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?

Clearly states the action (sync), the resource (Local JSON changes), and the method (via WP-CLI command). Distinct from sibling tools which handle creation, deletion, import/export, etc.

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?

Implies use for syncing Local JSON, but does not specify when to use this tool versus alternatives like acf_import_json. No explicit when-not or prerequisites.

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