preflight_check

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true. The description adds valuable behavioral context by enumerating the specific safety checks (page existence, Elementor-build, data parsing, global widget references, lock status). There is no contradiction with annotations.

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, well-structured sentence that starts with the core purpose and lists specific checks efficiently. Every part earns its place without redundancy.

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 presence of an output schema and the thorough annotations, the description sufficiently covers the tool's behavior. It enumerates all key validation points and implies the output will indicate pass/fail. The sibling context further clarifies its role as a pre-edit check.

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% for the two parameters. The description does not explain the meaning of 'site_id' or 'page_id', nor how they map to the checks. It only implies page_id identifies the page but lacks details like expected format or that site_id is optional.

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 a specific verb 'Validate' and clearly identifies the resource 'a page is safe to edit' with a detailed list of checks. This distinguishes it from sibling tools like 'read_page_elementor' or 'update_widget_settings' that perform different operations.

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 strongly implies use before editing a page, listing conditions that must pass. However, it does not explicitly state when to avoid this tool or mention alternatives for similar validation tasks.

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