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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral context beyond that: the tool degrades gracefully without an SEO plugin, skipping meta description and focus keyword checks. It does not mention rate limits, auth requirements, or what the recommendations payload looks like.

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?

Three tight sentences: purpose first, then the checks, then the plugin-optional caveat. Every sentence carries information and nothing is padded.

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 read-only analysis tool with full schema coverage and no output schema, the description covers purpose, scope of checks and the plugin-conditional behavior. The only gap is that it promises 'actionable recommendations' without any hint of their shape or severity grading, which would help an agent know what to do with the result.

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, post_type and focus_keyword are all documented in the schema itself, including the 'optional if you have only one connected site' and 'will use stored keyword if available' fallbacks. The description's mention of focus keyword checks adds only marginal meaning beyond the schema, so the baseline 3 is appropriate.

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 ('Analyze a post/page for SEO best practices') and enumerates the exact checks performed (title length, meta description, keyword usage, content length, headings). It is clearly distinct from the read-only sibling seo_get_post_meta, though it never names or contrasts that sibling explicitly.

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 implies usage by describing what gets checked and notes the plugin-optional behavior, but gives no explicit when-to-use/when-not guidance and never routes the agent between this tool and seo_get_post_meta or the wp_* content tools. Usage must be inferred from the enumerated checks.

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