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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds context the annotations cannot: dry_run defaults to true and only launches when false, and that all prior stages must be approved with a confirmed email. It does not say what happens to an existing draft or what a launch consumes, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the trigger and followed by the dry_run rule and the prerequisites. Nothing is wasted, though dry_run is explained twice within a very short span, once in the description and once in the schema, which is mild redundancy.

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, four-parameter action tool with no output schema, the description covers the essentials an agent needs: when to invoke, the safe default, and the approval/email gates. The remaining gap is consequence detail - whether a generated draft replaces a prior one and any quota cost - which matters given destructiveHint=true.

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 75% and the schema already documents dry_run, project_id and idempotency_key thoroughly. The description restates the dry_run default/false behaviour without adding syntax or caveats, and says nothing about idempotency_key. Baseline 3 is appropriate when the schema is doing the explanatory work.

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 artifact: writing the 'manuscript draft' from 'approved stages (action manuscript)', which pins down both the operation and the enum value. It is clear on its own, though it never explicitly contrasts itself with the sibling read tool 'revisia_report' or the export tool, so differentiation is left to inference.

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 an explicit trigger ('Use this when the researcher wants the manuscript draft written') plus preconditions: every earlier stage must be approved and an email confirmed. What is missing is the negative case - no statement of when not to call this versus revisia_report or revisia_export - but the gating conditions are unusually concrete for this suite.

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