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

The annotations already signal a destructive write (readOnlyHint=false, destructiveHint=true), and the description adds concrete behavioral detail: 'Clears Agree,' 'Does not run,' and the write-tier approval workflow including 'a from-now-on approval' vs 'a just-once approval.' It also tells the agent to act on the first clear ask rather than re-asking in chat. No contradiction with the annotations.

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 dense but economical: purpose, side effects, trigger conditions, routing, and approval behavior each get their own concise sentence or clause. There is no filler, and the most decision-relevant content is front-loaded at the start.

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 destructive tool with no output schema, the description covers when to use it, what it destroys ('Clears Agree'), what it does not do, approval requirements, and follow-up routing to get_playbook. It could be more complete by explicitly noting what the tool returns or how it relates to redraft_engine_playbooks, but the essentials are present.

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?

All four parameters are fully described in the schema (100% coverage), including force, companyId, playbook_id, and playbook_title. The description does not add parameter-level nuance beyond the schema, so the baseline of 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?

The description names a specific verb and resource: 'Rewrite one engine-drafted Play into an English operator contract,' and defines the output as 'outcome, who, what Yes authorizes.' It distinguishes itself from run_playbook/agree_playbook with 'Clears Agree' and 'Does not run,' and narrows scope to a single Play, which separates it from the sibling redraft_engine_playbooks.

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 explicit trigger conditions: 'Use on first Focus view leftovers or when get_playbook still shows an activity slug as the title,' plus a routing line: 'Engine slug Play → English contract → use this, then get_playbook.' It does not directly name the closest alternative (redraft_engine_playbooks) or state when to choose that instead, so the guidance is strong but not fully comparative.

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