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

Adds substantial behavior beyond the annotations: partial-update semantics, HTML/newline stripping, the non-obvious side effect that noindex=False overrides the site default, the response echo plus 'updated' field list for verification, and the ambiguity of timeout errors where the write may or may not have landed. This goes well past destructiveHint/openWorldHint.

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?

Front-loaded with the core action and partial-update rule, then field semantics, then prerequisites and error handling. Dense but every clause carries information; the dash-separated error section is slightly compressed and could be split for readability.

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 a destructive write tool with 0% schema coverage, it covers prerequisites, per-field semantics, verification, and ambiguous-failure handling. Return values are summarized despite an output schema existing, so an agent has everything needed to call and verify 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%, so the description must carry parameter meaning, and it does for title, description, canonical, noindex (including the True vs False asymmetry) and workspace (optional with a single workspace). Only post_id, the one required parameter, is left unexplained beyond implication.

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: writes SEO metadata (Yoast/Rank Math) of a WordPress page, and specifies that only supplied fields are changed. The write-vs-read distinction against the sibling wp_seo_get_meta is implicit in 'schreiben' and the read-back note, but the sibling is never named, so it stops short of explicit differentiation.

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?

Gives actionable operating conditions: at least one field required or the call returns no_changes, empty string resets to plugin default, and the Honeyfield connector plugin must be present (pointing to wp_bridge_status). Error guidance for wp_timeout/wp_unreachable ('check first, don't blindly retry') is genuinely useful. It lacks an explicit statement of when to prefer this over wp_seo_get_meta or wp_update_post.

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