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

The description states 'no external research or outbound actions' and 'Returns a draft for human review,' implying a safe, non-destructive read operation. However, annotations declare openWorldHint: true and destructiveHint: true, which directly contradict the description. This is a serious inconsistency, so the score is 1 as per the contradiction rule.

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 concise, only four sentences, and clearly front-loads the core purpose. It includes relevant operational details (no external research, draft output, pricing, payment authorization) without fluff. However, it could be slightly more structured by separating pricing/payment into a distinct note, but overall it is efficient.

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 tool's complexity (5 parameters, nested input, no output schema), the description is incomplete. It does not explain the input requirements beyond the schema, nor the exact return format or how the draft is delivered. It also leaves the purpose of fields like result_expires and payment_signature unexplained, relying entirely on the schema. The payment authorization note is useful but not sufficient for an agent to invoke correctly.

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% – the description does not mention any parameter names, their purposes, or how to construct the nested input object. The schema itself provides properties like brief, source_text, and audience, but the description adds no meaning beyond that. For a tool with 5 parameters and a nested object, the description should compensate, and it completely fails to do so.

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 clear and specific purpose: 'Review supplied copy and propose specific updates, evidence gaps, structural improvements, and freshness checks.' It names the exact resource (copy) and the actions (propose updates, identify gaps, etc.), which distinguishes it from generic SEO tools like seo_audit or seo_content_brief by focusing on refresh of existing content rather than audit or initial brief.

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 implies usage context: it reviews buyer-supplied copy without external research, and returns a draft for human review. However, it does not explicitly contrast with sibling tools (e.g., seo_audit or content_gap) or state when to prefer this over alternatives. The constraints are clear but not framed as a decision guide.

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