wordpress_analyze_seo

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

No annotations are provided, so the description carries full burden. It mentions analysis but doesn't disclose whether this is a read-only operation, what permissions are required, whether it makes any changes to the post, what format the analysis returns, or any rate limits. For an analysis tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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 extremely concise - just one sentence with 5 words. It's front-loaded with the core purpose. While appropriately sized for what it covers, it's arguably under-specified rather than efficiently concise.

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 no annotations, no output schema, and 0% parameter description coverage, the description is incomplete. It doesn't explain what the analysis returns, what SEO elements are examined, or any behavioral aspects. For an analysis tool that presumably returns structured data about SEO, this leaves too many questions unanswered.

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?

The input schema has 1 parameter with 0% description coverage. The description doesn't mention the 'postId' parameter at all, nor does it explain what constitutes a valid post ID, whether it refers to published posts only, or any constraints. With low schema coverage, the description fails to compensate for the undocumented parameter.

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 states the tool's purpose as analyzing SEO elements for a post, which is clear but vague. It specifies the resource (post) and general action (analyze SEO elements), but doesn't detail what specific SEO elements are analyzed or how the analysis is performed. It doesn't distinguish from siblings like 'wordpress_set_seo_meta' or 'wordpress_set_canonical_url' which are also SEO-related.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, timing considerations, or how it differs from other SEO-related tools in the sibling list. There's no indication of when this analysis would be appropriate versus setting SEO metadata directly.

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