wp_seo_get_live_data

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

No annotations are provided, so the description carries the full behavioral burden. It doesn't disclose whether the call is read-only, whether it triggers network requests to plugins, latency expectations, auth requirements, or what 'live' implies operationally.

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?

One compact sentence with the verb and scope front-loaded; no waste. It is terse but appropriately sized for a simple getter.

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 an SEO data retrieval tool surrounded by many SEO siblings, the description omits what data is returned, which plugins are involved, and how it relates to siblings. With no annotations and no output schema, more context is needed to call it confidently.

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 coverage is 100% and the single 'site' parameter is fully documented in the schema, so the description adds no parameter meaning beyond it. Baseline 3 applies when the schema does the work.

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?

States a verb and resource ('Retrieve live SEO data from WordPress') plus scope ('plugin-specific metadata and configurations'). But it doesn't distinguish this tool from SEO siblings like wp_seo_site_audit, wp_seo_analyze_content, or wp_seo_test_integration, leaving ambiguity about what 'live data' means versus those alternatives.

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 indication of when to use this tool versus the many other SEO tools (site audit, content analysis, SERP tracking, integration test). No prerequisites or exclusions are given, so the agent must guess 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.