Aktualisiere WordPress Post

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states that the tool updates a post, without mentioning that it may overwrite existing fields, whether unspecified fields remain unchanged, whether specific permissions are required, or what the response format is. This lack of detail is a significant gap for a mutating operation.

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, concise sentence that communicates the core function without any unnecessary words. It is appropriately 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?

Despite having an output schema, the description lacks critical behavioral context for an update operation. It does not explain how partial updates work, whether setting fields to null is possible, or what the result indicates. The combination of no annotations and a minimal description makes this tool under-specified for reliable agent use.

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?

The input schema provides detailed descriptions for all 8 parameters (100% schema coverage), so the description doesn't need to add parameter-level details. The baseline of 3 is appropriate because the schema already covers parameter semantics effectively; the description adds no additional insight beyond the schema.

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's purpose: 'Aktualisiert einen bestehenden WordPress-Beitrag' (Updates an existing WordPress post). It specifies a concrete action (updates) and resource (existing WordPress post), distinguishing it from siblings like wp_create_post, wp_delete_post, and wp_update_page.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or context such as 'use for modifying an already published post.' The only implicit information is from the tool name itself.

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