acf_create_field_group

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It omits details about idempotency, error handling (e.g., duplicate key behavior), side effects, or required permissions, leaving the agent uncertain about the operation's impact.

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 but lacks structure. For a tool with seven parameters and nested fields, a brief phrase is inadequate for proper understanding. It could be expanded with bullet points or a short paragraph.

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 complexity (multiple parameters, nested objects, no output schema) and 57% schema description coverage, the description is incomplete. It does not explain the return value, error states, or integration with other ACF tools, leaving the agent without critical 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?

The description adds no information beyond what is already in the input schema. While schema coverage is 57%, the description does not clarify parameter relationships, defaults, or constraints (e.g., how 'location' rules work or 'fields' structure). It fails to compensate for the missing 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 the action ('Create') and the target resource ('ACF field group') with a specification of content ('with fields'). This effectively distinguishes it from sibling tools like acf_delete_field_group or acf_get_field_group.

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 (e.g., acf_update_field_group for modifications) or any prerequisites (e.g., existing field group skeleton). It fails to set usage context.

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