wp_seo_test_integration

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

No annotations are provided, so the description carries full behavioral disclosure burden. It doesn't state what 'test' entails (e.g., read-only detection vs. making changes), whether authentication is required, what happens if no SEO plugin is found, or the nature of the test 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 is front-loaded with the primary action and secondary detection purpose.

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?

With no annotations, no output schema, and only a brief description, the tool definition is incomplete for an agent to call it correctly. It lacks details on what the test does, what it returns, and under what conditions it should be invoked relative to other SEO tools.

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 100%, so the single 'site' parameter is fully documented in the schema. The description adds no additional meaning about the parameter beyond what the schema provides, which is the baseline expectation when schema coverage is high.

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 a clear dual purpose: test SEO plugin integration and detect available SEO plugins. It's a specific verb+resource, though it doesn't explicitly differentiate itself from related SEO siblings like wp_seo_get_live_data or wp_seo_site_audit.

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 on when to use this tool versus alternatives. It doesn't say whether to call it before or after SEO operations, or what triggers its use. The implied usage is diagnostic, but no conditions or exclusions are provided.

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