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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), so the bar is lower. The description still adds real value: it explains that values are read as the active provider stores them, defines robots_explicit=false as 'provider default applies', and states a Connector version prerequisite — none of which the annotations or schema convey.

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 read operation and returned fields, then use cases, then a semantics note and a prerequisite. Dense but each sentence earns its place; the homepage-omission clause mildly duplicates the schema.

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 carries the burden of explaining returns and does so by enumerating the four fields plus the meaning of robots_explicit. Combined with annotations covering safety and the site_id/post_id contract, an agent has enough to call it 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 coverage is 100%, so both parameters are already documented. The description restates the homepage/post_id omission rule already in the schema and adds no new parameter detail (its robots_explicit note refers to a returned field, not an input). 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?

It states a specific verb (read) plus the exact resources returned — SEO title, meta description, robots directive and canonical URL — and names the plugin contexts (Yoast/RankMath/AIOSEO) it reads from. An agent can distinguish this from the sibling wp_set_seo_meta without opening either schema.

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?

It gives two concrete use cases: carrying SEO fields from a source page to its copy, and confirming a noindex landed before publishing. This sets clear context and implies the read-before-write pairing with wp_set_seo_meta, though it never names that sibling as the alternative explicitly.

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