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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior beyond that: how to interpret empty title/description (plugin template applies, not missing), what noindex:false means, the specific error hf_no_seo_plugin, and the wp_timeout / wp_unreachable failure modes with a retry instruction. The plugin-dependency prerequisite is exactly the kind of context annotations cannot carry.

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 purpose is front-loaded and nearly every sentence carries unique information. The ordering is slightly scattered (error codes appear before the parameter explanations), and the param notes trail the failure-handling text, which costs a bit of scannability.

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?

Given an output schema exists, return values need not be re-specified, and the description instead supplies interpretation rules, prerequisites, and error recovery. For a two-parameter read tool with failing external dependencies, nothing an agent needs in order to call it correctly is missing.

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 carries the full burden, and it does: post_id is defined as a numeric post/page ID sourced from wp_list_posts, and workspace as a customer-workspace slug that is optional when only one workspace exists. Both parameters gain meaning that the bare schema does not provide.

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 first clause names a specific verb and resource (SEO-Metadaten ... lesen) and enumerates the exact fields returned (seo_plugin, title, description, canonical, noindex). It also implicitly distinguishes itself from the write sibling wp_seo_update_meta by being a read operation, and the plugin scope (Yoast/Rank Math) narrows the domain precisely.

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 gives a clear usage condition that matters most: these fields are protected post-meta and not reachable via the normal WP REST API, so the Honeyfield connector is required (with a pointer to wp_bridge_status). It also says where post_id comes from (wp_list_posts). It does not explicitly name wp_get_post or wp_seo_update_meta as alternatives, so it falls short of full when/when-not guidance.

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