seo.set_meta.v1

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

No annotations are provided, so the description carries the full behavioral burden. It indicates 'Update' implies mutation but doesn't disclose whether the change is reversible, whether it requires specific permissions, how partial updates (title only vs description only) are handled, or what happens to the other field when only one is provided. This is a write operation with no safety disclosure.

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 with zero waste. It's appropriately brief, though it could have used the space to add parameter clarification rather than just restating the tools' purpose.

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?

Despite having a simple 3-parameter schema with 1 required parameter, the description is thin for what is presumably a key SEO editing operation. There's no output schema explanation (though the tool has one in the output), no mention of validation behavior, and no note about how the custom endpoint differs from standard Yoast updates. The tool updates permanent SEO metadata, which warrants more behavioral disclosure.

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 0%, so the description must compensate for parameter documentation. The description mentions 'title and/or meta description' which maps loosely to the 'title' and 'description' parameters, but doesn't explain the semantics of partial updates (e.g., what happens if only title is provided). The 'post_id' parameter requirement is implied but never explained.

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 Yoast SEO title and/or meta description via custom endpoint' clearly states the verb (update), resource (Yoast SEO title/meta description), and indicates it's a custom endpoint. However, it doesn't distinguish itself from the sibling 'update_yoast' tool which appears to serve the same purpose, creating ambiguity about which to use.

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?

The description provides no guidance on when to use this tool versus alternatives. Notably, there's a sibling tool named 'update_yoast' that likely serves a very similar purpose, yet no distinction or recommendation is offered. No prerequisites or context for when this custom endpoint should be preferred.

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