Apply ACF Content Model

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'dependency-safe order' but does not explain what 'apply' entails (create/update/overwrite), side effects (e.g., writing to local JSON), or prerequisites (e.g., ACF PRO active). More detail is needed for full transparency.

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 that efficiently conveys the core functionality with no wasted words.

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 complexity of the input schema (nested objects, multiple required fields) and the lack of an output schema, the description is too brief. It does not explain return values, the meaning of 'apply' (e.g., writes to JSON, no server-side effect), or the behavior of the backup and dryRun parameters.

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 0%, yet the description only lists the categories of content types without explaining individual parameter fields, validation rules, or structure. It adds minimal meaning beyond the property names in the schema.

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 tool's purpose: applying a declarative content model to Local JSON in dependency-safe order, listing the content types (post types, taxonomies, options pages, field groups). This distinguishes it from sibling tools that handle individual CRUD operations for each type.

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 implies usage for bulk applying a content model, but does not explicitly contrast with using individual create tools for single entities. The mention of 'dependency-safe order' gives some guidance on when this tool is appropriate.

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