update_seo_data

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Update' implying a mutation, but doesn't disclose critical behaviors: whether it overwrites all fields or partial updates, if it requires specific permissions, what happens on success/failure (e.g., returns updated data or just confirmation), or any rate limits. The description lists fields but lacks operational context.

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 that front-loads the action ('Update Rank Math SEO data') followed by a comma-separated list of fields. It avoids redundancy and wastes no words, though it could be slightly more structured (e.g., grouping related fields). Every part earns its place by specifying the scope.

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 complexity (9 parameters, mutation operation) and lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success status, updated SEO data), error conditions, or behavioral nuances like partial updates. For a mutation tool with rich parameters, more context is needed to guide effective use.

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 schema already documents all 9 parameters thoroughly (e.g., post_id as 'Post or page ID', seo_description with character recommendations). The description adds minimal value by listing field names like 'SEO title, meta description' but doesn't provide additional syntax, constraints, or examples beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the verb 'Update' and resource 'Rank Math SEO data', listing specific fields like SEO title, meta description, focus keyword, etc. It distinguishes from sibling tools like 'get_seo_data' by specifying an update operation, but doesn't explicitly differentiate from other update tools like 'update_element' or 'update_post' beyond the SEO focus.

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. It doesn't mention prerequisites (e.g., needing a valid post_id), when not to use it (e.g., for non-SEO updates), or refer to sibling tools like 'get_seo_data' for checking existing data before updating. The description assumes context without explicit instructions.

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