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

Even though the annotations already declare readOnlyHint and idempotent, the description adds substantive behavior beyond them: the edit-post capability requirement, the not-found error for unknown post_id, and how fields vanish under AIOSEO or unsupported plugins with an explanatory note.

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-loads the return shape and plugin caveats, and every clause carries content. The trailing AlphaBridge forwarding sentence is relevant but slightly dilutes focus.

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?

With no output schema, the description compensates fully by spelling out the returned object keys, the empty-field convention, and the plugin-dependent degradation. An agent has everything needed to call it and interpret the response.

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 coverage is 100% and the single parameter is already documented as the post/page id. The description restates the single-post scoping and the unknown-id error, adding modest value but no syntax or format detail 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?

States a specific verb and resource ('Get the SEO title, meta description and focus keyword of one post') and scopes it to the Yoast/Rank Math storage model. It explicitly differentiates from siblings by naming wp_seo_detect as the plugin-detection-only alternative.

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 clear context for use (reading SEO fields for a single post) and routes the agent away from wp_seo_detect when only the plugin needs to be identified. It does not explicitly state when not to use it (e.g., bulk reads), keeping it just below a 5.

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