wp_update_draft_post

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

With no annotations, the description discloses key behaviors: only updates drafts, creates new draft if published, and never publishes. However, it omits details like required permissions, response format, or effects on the original post when creating a new draft.

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?

Description is two sentences with no wasted words. First sentence states main action, second adds critical nuance. Information is front-loaded and easy to parse.

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?

Tool has 7 parameters, no output schema, and no parameter descriptions. Description lacks return value information, error handling (e.g., invalid id), and idempotency. Agent would need to infer many details from context.

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%, so description must compensate but only explains tool behavior, not parameter details. It does not add meaning to parameters like id, title, or tags beyond their names. Schema property names are self-explanatory but description fails to provide additional context.

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?

Description clearly states 'Update an existing DRAFT post' with a specific verb and resource. It distinguishes from siblings like wp_create_draft_post by noting the tool updates existing drafts and cannot publish, which differentiates it from creation and publishing tools.

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?

Description provides clear usage context: use for existing drafts, not for published posts (creates new draft instead). It implicitly contrasts with wp_create_draft_post for new drafts, but does not explicitly list alternatives or when-not-to-use scenarios.

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