wordpress_analyze_seo

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

Without annotations, the description bears full responsibility for behavioral disclosure. It states 'analyze,' implying read-only, but does not confirm that the tool does not modify data, explain required permissions, or describe the output format. This leaves the agent with uncertainty about side effects and results.

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, efficient sentence with no wasted words. It could be slightly more informative without adding length (e.g., specifying the type of analysis), but it is not verbose.

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 simple tool with one parameter and no output schema, the description provides minimal context. It differentiates from siblings via the verb 'analyze,' but does not explain what the analysis output contains or how to interpret it. Given the many sibling tools, more detail on the analysis scope would improve completeness.

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 coverage is 0%, so the description should add meaning to the parameter 'postId.' However, the description does not mention 'postId' at all. Although the parameter name is self-explanatory, the description provides no additional context beyond the schema, resulting in baseline value.

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 'Analyze SEO elements for a post' clearly states the action (analyze) and resource (SEO elements for a post), distinguishing it from sibling tools that get, set, or delete. However, it does not specify which SEO elements are analyzed (e.g., meta tags, keywords, readability), leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives like wordpress_get_post (which might return SEO data) or wordpress_set_seo_meta (for modification). An agent must infer usage from the name alone.

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