wp_analyze_page_seo

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only lists what is analyzed but does not state whether the tool modifies data, requires authentication, or has side effects. For a read-like analysis tool, this omission is a significant gap.

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?

The description is a single sentence that is front-loaded with the action and concisely lists the aspects analyzed. There is no waste, and every word earns its place.

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?

Given high schema coverage and a straightforward analysis purpose, the description adequately covers what the tool does. It lacks specification of output format, but the lack of output schema and presence of sibling tools like wp_generate_content_report mitigate this need.

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?

Input schema has 100% coverage with clear descriptions for both parameters: 'Page ID' and 'Search page by title instead of ID'. The description adds no extra parameter information beyond what the schema provides, so 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?

The description clearly states the verb 'Analyze', the resource 'a page', and specifies the aspects analyzed: headings, keywords, meta, internal links, readability. This distinguishes it from sibling tools like wp_analyze_post_seo (for posts) and other SEO-related tools.

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 for SEO analysis of pages but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. Without exclusions, the agent must infer context from sibling tool names, which is adequate but not explicit.

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