acf_import_field_groups

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

No annotations exist, so the description must disclose behavioral traits. It only states the import action but omits critical details: whether existing groups are overwritten, permission requirements, error handling for invalid JSON, or destructive potential.

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 clear sentence, front-loaded with the verb 'Import', with no unnecessary words. It is appropriately sized for a simple import operation.

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 lack of annotations, output schema, and complexity of an import operation (overwrites? duplicates?), the description is incomplete. It does not address error conditions, idempotency, or what happens on success/failure.

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 100% for the single 'groups' parameter. The description adds minimal extra meaning ('from JSON export format') beyond the schema's 'Array of ACF field group JSON objects'. Baseline 3 applies.

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 'Import' and resource 'ACF field groups from JSON export format', clearly distinguishing it from sibling tools like acf_create_field_group (manual creation) and acf_export_field_group (export).

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 vs alternatives (e.g., acf_create_field_group for manual entry). No prerequisites, exclusions, or context about overwriting or merging behavior.

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