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

The description adds useful behavioral detail beyond annotations: idempotence per day, the SLOW LLM-call cost, and force/slot semantics. However, it directly contradicts the destructiveHint:false annotation by saying force=true wipes today's PENDING drafts first; wiping is destructive. Per rubric, the contradiction forces a score of 1.

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 short and front-loaded with the purpose, and each following sentence covers a distinct operational concern (idempotence, force, slot targeting, cost). The hyphenated guard phrases are somewhat jargon-heavy but do not bloat the text.

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 5-parameter generation tool with no output schema, the description covers core behavior, idempotence, and cost, but it never states what the tool returns or how the active flow is determined. No output schema means the description should at least describe the result shape, so the definition is not fully complete.

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 coverage is 80% and the description adds meaning where it matters: force has no schema description but the description defines its destructive re-run behavior, and slot_index is tied to asset flows and `_s{n}` draft ids. It doesn't describe context, but the schema already does, so the added value is strong.

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 specific action and scope: it runs the daily draft engine to generate today's pending drafts for the active flow. This distinguishes it from sibling tools like regenerate_draft and list_drafts, whose names imply different operations.

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 clear context: run for the day's pending drafts, re-running fills gaps, force is for wiping pending drafts first, and slot_index lets a single failed slot be re-fired. It does not explicitly name alternatives or exclusions, but the intended triggers are inferable from the operational description.

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