wordpress_update_theme_json

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Update' implying a mutation, but fails to describe critical traits like required permissions, whether changes are reversible, potential side effects on site appearance, or rate limits. This leaves significant gaps for a mutation tool.

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, efficient sentence with zero wasted words, front-loading the key action and resource. It's appropriately sized for the tool's scope, making it easy to parse quickly.

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 (mutation with a nested object parameter), lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't cover behavioral risks, parameter details, or expected outcomes, making it inadequate for safe and effective use by an AI agent.

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%, so the description must compensate for undocumented parameters. It only mentions 'theme.json configuration' without explaining the 'themeJson' parameter's structure, format, or valid values. This adds minimal meaning beyond the schema, insufficient for a tool with a complex nested object parameter.

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 ('Update') and target resource ('theme.json configuration for block themes (FSE)'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'wordpress_get_theme_json' or 'wordpress_update_settings', which could handle similar configurations, so it misses full sibling distinction.

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, such as 'wordpress_update_settings' for general settings or 'wordpress_get_theme_json' for retrieval. It lacks context about prerequisites, like needing block themes or specific permissions, leaving usage unclear.

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