Full editorial QA report

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

No annotations are provided, so the description carries the burden. It discloses that the SEO check only runs on HTML input, which is a behavioral constraint. However, it doesn't mention whether the tool is read-only or if it has any side effects, rate limits, or other behavioral traits. The description is honest but not exhaustive.

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 two sentences, front-loaded with the core purpose and the key constraint about HTML. Every sentence earns its place, and there is no fluff.

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 (running multiple checks) and the absence of an output schema, the description does a good job of setting expectations: it returns a single report with fixes attached. It could mention the format of the report or whether it's a summary, but the description is adequate for an agent to decide to call 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?

Schema description coverage is 100%, so the schema already documents both parameters. The description adds context that 'input' can be raw HTML or plain text and that HTML is preferred, which is useful. It doesn't add much about 'focusKeyword' beyond what the schema says, but the schema already covers it. Baseline 3 is appropriate.

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 clearly states the tool runs every check (readability, AI-writing tells, on-page SEO) on one article and returns a single report. It distinguishes itself from the sibling tools by being the comprehensive 'full report' option, while the siblings are individual checks.

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 when to use this tool: when you want all checks at once. It also provides a clear preference for HTML input and notes that the SEO check only runs on HTML. However, it doesn't explicitly state when to use the individual sibling tools instead, though the distinction is fairly obvious from the name and description.

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