wp_elementor_repair_json

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

There are no annotations, so the description carries the full burden of disclosing behavior. It does reveal that the tool re-saves and modifies Elementor JSON, but it does not mention side effects such as whether existing layout changes are overwritten, whether a backup or revision is recommended, whether permissions are needed, or whether the operation is reversible. For a mutating repair operation, this is a meaningful gap.

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 two sentences, front-loads the core action, and includes a concrete example. Every sentence earns its place with no redundant or vague filler.

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?

The tool is simple (one required parameter, no nested objects, no output schema), and the description provides a clear purpose and trigger. However, it lacks important operational context such as side effects, the exact meaning of page_id, and what to expect after execution, making it adequate but not fully complete.

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 schema provides only 'page_id' as an integer with no description, and schema description coverage is 0%. The description mentions 'a page' but never explains that page_id is the WordPress page/post ID or how to obtain it. The description does not meaningfully compensate for the missing parameter documentation.

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 a specific action ('Re-save Elementor JSON on a page') and an explicit purpose ('fix corruption'), with a concrete symptom example ('$400n heading text'). It is understandable and distinct from the related page/Elemenator tools, though it does not explicitly differentiate itself from siblings like wp_elementor_regenerate_css.

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 clear context for when to use the tool: 'Use after duplicate issues or broken templates.' It gives situational triggers but stops short of stating when not to use it or naming alternative tools, so it has no exclusions but is still useful guidance.

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