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

Annotations already indicate a non-read-only, idempotent operation, and the description adds substantial behavioral context: server-side validation of revision, method availability, runner configuration, reviewed capabilities, consent, and idempotency key; refusal of the entire run when source material is unreadable; and the MCP file:// limitation. No contradiction with 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 purposeful, with each sentence contributing operational guidance: single-run behavior, confirmation requirement, server validations, file:// constraint, and readability refusal. It loses one point for mild redundancy about explicit confirmation and a long validator list that could be slightly tightened.

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 an 11-parameter, high-stakes execution tool with no output schema, the description covers the essential preconditions, failure modes, and invocation constraints: confirmation, monolithic execution, idempotency, advanced-method opt-in, file path limitations, and source-material accessibility. Combined with the detailed schema, an agent has sufficient context to call it 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 every parameter is already documented in detail. The description reinforces the confirmation gate, idempotency key role, and advanced-method consent, but it does not add significant meaning for individual parameters beyond what the schema already 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 clearly states that this tool 'Executes the exact stored multi-question draft revision inside the target Study after explicit confirmation.' It also clarifies the critical distinction from fragmented usage: one execution submits the entire draft as one durable run, not per-question or per-module runs.

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?

The description explicitly says this operation is valid only after explicit confirmation, and gives a clear 'never' instruction against executing questions separately or creating per-module runs. However, it does not name alternative sibling tools, such as plan_study_questions or get_study_run, so routing guidance is present but not fully complete.

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