Aktualisiere WordPress Seite

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description is a tautology—'updates an existing page'—and does not mention side effects, required permissions, partial update behavior, or the impact of omitting fields.

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 sentence with no unnecessary words, front-loaded with the core purpose. It is concise, though it sacrifices valuable context for brevity.

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?

The description is severely incomplete for a 7-parameter mutation tool. It lacks usage guidance, parameter semantics, and behavioral transparency, and does not leverage the existence of an output schema to clarify expectations. An agent would struggle to invoke this tool 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 only 14%, and the description adds no parameter details. It does not explain what `slug`, `title`, `parent`, `status`, `content`, or `template` mean or how they should be formatted, leaving the agent without essential information.

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 clearly that it updates an existing WordPress page, using the specific verb 'Aktualisiert' and resource 'bestehende WordPress-Seite'. It distinguishes itself from related sibling tools like wp_create_page (create) and wp_update_post (post vs 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?

No guidance is provided on when to use this tool compared to alternatives like wp_update_post or wp_create_page. There are no stated conditions, prerequisites, or exclusions; the description only restates the core action.

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