seo_update_term_seo

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a mutation ("Update") but says nothing about required permissions, whether unspecified meta fields are preserved or cleared, or what the response contains. This is a significant gap for a 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?

A single, front-loaded sentence with zero waste. It is appropriately sized for what it communicates, though it is quite sparse for a mutation tool with a nested meta object.

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?

The tool is a mutation with a nested meta object, no annotations, and no output schema. The description does not explain the meta object's expected fields, whether existing fields are merged or replaced, or any side effects. Given this complexity, the definition is incomplete.

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 site, id, and meta. The description adds no additional meaning beyond identifying the target as a taxonomy term, which is already implied by the tool name and parameter descriptions.

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 states a specific verb (Update) and resource (SEO meta for a taxonomy term), which distinguishes it from seo_update_post_seo and seo_get_term_seo. It is clear enough for an agent to identify the operation, though it does not explicitly call out the sibling 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?

There is no guidance on when to use this tool versus alternatives like seo_get_term_seo or seo_update_post_seo, nor any prerequisites or context about when a term's SEO meta should be updated. The description provides only a bare statement of function.

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