Update WordPress Page

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

Annotations already indicate destructive and non-read-only behavior. The description adds meaningful behavioral context: partial update semantics, content_path overriding content, and the output format default. No contradictions 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 concise and well-structured, with a front-loaded purpose statement, clear Args list, and Returns line. Every sentence adds information without redundancy or bloat.

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?

For a destructive update tool with 13 parameters, the description covers partial update behavior, the content_path use case, and the return type. It lacks details on error conditions or authorization, but annotations and schema provide sufficient safety context. Overall complete for typical usage.

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 coverage is 100%, so baseline is 3. The description adds value by explicitly noting id is required and all other fields optional, and by explaining content_path overrides content. This exceeds the baseline by providing cross-referential clarity.

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 'Update an existing page' with a specific verb and resource, distinguishing it from create operations. The reference to wp_create_page for field shape further clarifies the tool's scope. No ambiguity with sibling tools like wp_update_post.

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 updating existing pages with partial field updates ('Only the fields you pass will change'), but does not explicitly state when to use this tool versus alternatives like wp_update_post or wp_delete_page. The cross-reference to wp_create_page is helpful but not a full alternatives discussion.

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