wp_seo_bulk_update_metadata

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

No annotations provided; description mentions 'progress tracking and error handling', adding some behavioral context beyond the schema. However, it omits details like authentication needs, rate limits, or whether changes are reversible, which are important for a mutation tool.

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?

Single sentence, concise and front-loaded. The phrase 'with progress tracking and error handling' is somewhat vague but not overly lengthy. Could be tighter if those details are not critical.

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 (bulk update, nested object, no output schema), the description is adequate but lacks details on return values, error handling specifics, and progress tracking mechanism. More context would improve completeness.

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 parameters. The description adds no extra meaning to the parameters beyond labeling them as 'SEO metadata' and noting progress/error features, which are not parameter-level.

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 'Update SEO metadata for multiple posts with progress tracking and error handling' clearly specifies the action (update) and resource (SEO metadata for multiple posts), distinguishing it from single-post or analysis tools like wp_seo_analyze_content.

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 over siblings. For example, it doesn't contrast with wp_seo_generate_metadata or single-post update tools. The description implies bulk use but offers no explicit context.

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