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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and non-open-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: the same tool returns different scopes (site vs page) depending on the id, and enumerates the fields returned. Auth requirements and rate limits remain unstated.

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 action and returned data, then a second short paragraph on the id switch and the seo_audit tie-in. Two sentences with little waste, though the first sentence is a dense field-list that could be tightened.

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?

An output schema exists, so the description need not explain return values, and annotations cover the safety profile. It is largely complete, with the notable gap being that site_url goes unexplained and no default site-selection behavior is described.

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 must carry the parameter burden. It explains id well (absent = site level, present = page/post SEO fields), but site_url is never mentioned in either the schema or the description, leaving half the inputs undocumented for a tool that must identify which site to read.

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 (Read) and resource (SEO settings of a connected WordPress site) and enumerates the returned fields: SEO plugin, verification codes, meta title/description, canonical, focus keyword. It also scopes itself against a sibling by noting the page-level output is what seo_audit references when it flags a missing meta description.

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?

Explicitly tells the agent how to route: no id for site level, a page/post id for page-level SEO fields, and ties the latter to seo_audit's missing-meta-description finding. It lacks an explicit 'do not use this when...' or a contrast with the write counterpart wordpress_set_seo, so it falls short of the top mark.

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