Wordpress Update Post

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

No annotations are provided, so the description carries the full burden and delivers almost nothing. "Update" implies mutation, but it never states permission requirements, whether the update is partial (all non-post_id fields are null-defaulted), or what happens to fields left unset. With an output schema present, return values need not be explained, but the mutation semantics remain undisclosed.

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?

A single efficient sentence with zero waste, and the verb/resource are front-loaded. It is on the sparse side rather than bloated, so size is not the problem – content is.

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 an 11-parameter mutation tool with no annotations, the description is far too thin. With no safety profile, no partial-update behavior described, and no usage context, an agent lacks what it needs to call this correctly, even though the output schema covers returns.

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 the schema fully documents all 11 parameters (date, slug, tags, title, status, content, excerpt, post_id, categories, post_format, featured_media). The description adds no syntax, format, or validation detail beyond that, which is the correct baseline when the schema does the heavy lifting.

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?

States a specific verb and resource ("Update an existing WordPress post"), which is clear on its own. It does not, however, differentiate from siblings like wordpress_create_post or wordpress_update_page, nor indicate scope (e.g., partial vs. full update) – the agent must infer this from the schema.

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?

No when-to-use guidance, no exclusions, and no mention of the natural alternative (wordpress_create_post for new posts). The agent has to figure out from the name alone that this is for modifying existing posts identified by post_id.

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