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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine value by disclosing auto-detection across Yoast, RankMath, and AIOSEO, but says nothing about what happens when no plugin is installed or whether output is cached/limited.

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?

Two tight sentences: the capability and returned fields come first, the compatibility/auto-detection note second. Nothing is redundant with the title or schema, and there is no filler.

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 usefully enumerates the return values and explains multi-plugin support, which is the main ambiguity for this tool. It falls short only on edge cases (no SEO plugin installed, missing metadata) that an agent might reasonably need to know.

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 100%, so post_id, site_id, and the post_type enum are already documented in the schema. The description restates the post/page/product scope but adds no format, default, or constraint detail beyond the structured fields, so the baseline 3 applies.

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?

Specific verb + resource ('Get SEO metadata for a post, page, or product') with the exact returned fields enumerated (title, meta description, focus keyword, canonical URL). This clearly separates it from sibling reads like wp_get_post or seo_analyze_content, which cover content rather than SEO metadata.

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?

Usage is implied by the phrasing 'for a post, page, or product', and the plugin-compatibility sentence tells the agent it can call this regardless of which SEO plugin is active. However, there is no explicit when-to-use vs. when-not-to-use guidance and no named alternative (e.g., seo_analyze_content), so routing is left to inference.

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