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

Adds substantial context beyond the annotations: it creates a draft first if none exists, refuses with a reason when a brief cannot become a draft, the next crawl ticks checklist items, and the brief is Confirmed live only when title and H1 match. What it does not disclose is the consequence of destructiveHint=true — that a page goes publicly live and whether that can be undone.

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?

Purpose and address rules are front-loaded and every clause carries real information about publish, read-back, and confirmation. The long parenthetical sentence about views/position/clicks is genuinely hard to parse, which costs a point.

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 non-idempotent, destructive, multi-step tool with an output schema, the description covers the full lifecycle — publish, draft fallback, refusal, crawl read-back, Confirmed live criteria, downstream reporting, and cost. The only gap, undo/reversibility, is minor given the annotations flag destructiveness.

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 both the url default and the market/location_code alias are already documented in the schema. The description restates the url default but says nothing about 'fields' or 'keyword', so it adds little beyond structured data; baseline 3 applies.

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?

States a specific verb and resource — mark a content brief's page as live and publish its draft — and distinguishes itself from cvl_seo_draft_publish by framing that tool's publish step as a sub-behaviour of this one. An agent can tell what this does without opening the schema.

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?

Gives clear context: use it once the page is actually live, omit url to fall back to the brief's page, and re-saying with a new address restarts the read-back. It implies but never explicitly states the exclusion ("if you only want to publish and not mark live, use cvl_seo_draft_publish"), so routing is inferred rather than spelled out.

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