wordpress_analyze_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 disclosing side effects and behavior. 'Analyze' implies a read-only operation, but the description does not explicitly state non-mutation, return format, or any dependencies (e.g., an SEO plugin), leaving key behavioral aspects undisclosed.

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, front-loaded sentence with no filler or redundancy. It conveys the core purpose efficiently, though it could be more informative without losing conciseness.

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 the minimal schema, lack of annotations, and absence of an output schema, the description does not provide enough context for an agent to fully understand the tool's behavior or expected results. It does not specify which SEO elements are analyzed, what the output looks like, or whether any preconditions exist, making it a bare-minimum description.

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 only parameter, postId, is self-descriptive from its name, and the description ties it to 'a post'. However, with 0% schema description coverage, the description does not compensate by explaining the parameter's expected format, range, or that it is the WordPress post ID. The schema alone provides the type and requirement but little semantic context.

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 uses a specific verb ('Analyze') and clearly identifies the resource ('SEO elements') and target ('a post'). It is distinct from sibling tools that set or update SEO metadata, though 'SEO elements' remains somewhat vague without enumerating what those elements are.

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 like wordpress_set_seo_meta or wordpress_set_og_tags. The intended use is only implied by the word 'Analyze' and is not explicitly scoped or contrasted with other tools.

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