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

Annotations only cover safety flags (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds real behavior the annotations cannot: it refuses with needs_author_material, loops review→revise until no blockers/cadence findings and voice in range, appends a disclosure line, and requires Pro + Assist credits. It stops short of stating persistence/reversibility of the saved draft, but the disclosure and refusal semantics are substantial additions.

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?

Front-loaded with the hardest constraint (LAST-RESORT, Pro + Assist credits) and the material requirement, followed by refusal behavior, then the escalation condition. Dense but every clause carries distinct information; only the nested parentheticals slightly reduce scanability.

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, open-world writer tool with no output schema, the description covers prerequisites (author material, Pro + Assist credits), refusal behavior, the revision loop, side effects (disclosure line, saved draft), and the human-review boundary. An agent has everything needed to decide and 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 100%, so all three parameters are already documented. The description contextualizes max_passes (the review→revise loop) and save (the appended disclosure/stored draft), but adds no syntax, ranges, or defaults beyond what the schema states. 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 (drafts) and resource (the brief's piece) with a precise input constraint (from the AUTHOR'S OWN MATERIAL — interview answers and/or rough draft). It explicitly distinguishes itself from the sibling score_content_draft and from the default writer role, so an agent can place it 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 an explicit escalation trigger: 'use this when a draft has failed score_content_draft twice or the user asks for it,' plus the self-label 'LAST-RESORT WRITER.' It also states the negative condition (refuses when the brief has no author material), which is the strongest form of when-not guidance.

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