gold_wc_seo_meta_bulk

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

Annotations are absent, so the description bears the full disclosure burden. It discloses real behaviors: the exact target fields, plugin compatibility, and automatic trimming to 60/155 characters. It does not, however, warn that existing SEO titles and meta descriptions of all targeted products will be overwritten, and it is silent on return values and partial-failure behavior — material for a bulk write operation.

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 short and front-loads the verb and object in the first sentence, but it trails into three noise fragments ('POWER:', 'BYOK.', 'PAID ONLY PRO $29.') that are marketing or unexplained jargon. These fragments could earn their place if expanded, but as bare tokens they reduce clarity.

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 five-parameter bulk write with no output schema and no annotations, the description covers the essential operational traits (target fields, trimming, plugin mapping, PRO restriction). It omits the return/response behavior, the overwrite warning, and failure semantics for up to 25 products, which an agent would want before invoking it.

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?

With 80% schema coverage, the baseline is 3. The description fills the one coverage gap — the seo_plugin parameter, which has only an enum/default in the schema — by mapping each plugin choice to its concrete meta keys. It also reinforces the trim limits already documented in the schema, adding meaning without redundancy.

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 names a specific verb and resource ('bulk-set SEO title + meta description on many products') and goes beyond the name by listing the exact WordPress meta keys written (_yoast_wpseo_title/_metadesc or rank_math_title/description). This is clearly distinguishable from single-product tools by its bulk scope, though it does not explicitly name or distinguish a sibling like gold_wc_desc_bulk_byok, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance is given, and no alternative tools are named. The only hint is 'bulk ... on many products', which signals scale but leaves the agent to guess how this relates to the sibling bulk tools gold_wc_desc_bulk_byok, gold_wc_batch, or gold_update_product for single-item SEO edits.

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