wordpress_update_post

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It mentions updating a post but does not explain partial update semantics, what happens to unsupported properties, permission requirements, or return values. The claim 'can modify any post property' is vague and does not convey consequences.

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 sentence, concise and front-loaded with the action. It wastes no words, but its brevity leaves out necessary details. For a one-sentence description, it is structurally adequate.

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 flexible `updates` object and lack of output schema or annotations, the description is insufficiently complete. It does not explain allowed fields, merge behavior, or how it differs from bulk operations. The agent would need external knowledge to use it correctly.

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%, and the description does not compensate. It mentions 'any post property' but gives no specific property names, formats, or examples for the `updates` object. The nested structure remains ambiguous, so an agent would struggle to construct a valid request.

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 updates an existing post and can modify any post property, using a specific verb and resource. However, it does not explicitly distinguish itself from sibling tools like wordpress_bulk_update_posts or wordpress_update_page, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites mentioned, and no exclusions given. The description only states what it does, not when it is appropriate.

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