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

Beyond the readOnly/openWorld/destructive annotations, the description adds meaningful behavior: one bounded editorial response, local scoring, source checks, source-preserving edits, exact before/after scores, and a warning when the writing target is missed. It also cautions that results and speed may differ across hosts, which is useful non-obvious context.

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 first four sentences are front-loaded and informative, but the final sentence about 'Try and MCP use our hosted Zero Slop agent harness' is garbled and does not earn its place; it may confuse rather than guide an agent. The definition is otherwise compact and well ordered.

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?

With an output schema, full parameter coverage, and annotations, the description covers behavior, return value, failure mode, and appropriate use. Minor ambiguities like what 'source checks' or 'writing target' precisely include are left open, but they do not block correct invocation.

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 baseline is 3; the schema already documents text, genre, and audience. The description's 'pasted draft' phrasing reinforces the text parameter but adds no distinct meaning for genre or audience beyond what the schema provides.

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 concrete operation on a specific resource: it 'rewrite[s] a pasted draft' with an editorial response, local scoring, and source checks. It also names the outcome (source-preserving edit, before/after scores), so the tool's purpose is clear even without relying on the title.

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?

It gives a clear intended use ('improve writing quality') and explicit misuse boundaries ('never to hide authorship or evade a disclosure requirement'). There are no sibling tools to distinguish against, so the lack of alternatives is not a gap; it could only be improved by stating more concrete conditions or workflows.

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