wp_seo_track_serp

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

With no annotations, the description carries the full behavioral burden and falls short. It does not say whether tracking is a read or a persistent write, whether it requires an API key or configured SEO integration, how often rankings are refreshed, or what rate limits apply.

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?

A single, front-loaded clause with no filler or redundancy. Nothing needs trimming.

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 tool with no annotations and no output schema, the description should explain how keyword targets are specified and what the tracking result conveys. Instead it names keywords that appear nowhere in the schema, leaving a material gap.

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% for the single 'site' parameter, but the description introduces 'target keywords' as the operative input while no keyword parameter exists in the schema. That mismatch leaves the agent unsure how keywords are even supplied, which is worse than a neutral baseline.

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 specific verb and resource: 'Track search engine result page positions'. This is clearly distinguishable from sibling SEO tools like wp_seo_keyword_research or wp_seo_analyze_content, which serve different purposes. It does not, however, explicitly name which sibling it is not.

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?

There is no guidance on when to use this tool versus the many other SEO siblings (wp_seo_keyword_research, wp_seo_get_live_data, wp_seo_site_audit). No prerequisites, cadence, or exclusions are stated.

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