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

Beyond annotations that already flag destructive=true and idempotent=false, the description discloses the exact destruction scope ('replaces the prior summary without restore history') and what survives ('answers and questions are preserved'), plus the return format. This is precisely the added context annotations cannot convey.

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?

Four dense sentences with the mutation and its approval precondition front-loaded; the destruction/reversibility caveat follows immediately. Minor terseness ('force regenerates unchanged coverage') leans on the schema, but nothing is wasted.

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 mutation, the description covers the prerequisite, the irreversibility, the preserved data, and the return shape; with an output schema present, return values need no more detail. Only the missing pointer to the read-side sibling keeps it from being 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 75%, and the schema already documents force, study, and confirmed in detail. The description restates force's effect ('regenerates unchanged coverage') but adds nothing for study, length, or confirmed, so it neither undercuts nor meaningfully extends the schema.

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 pair and resource: 'Generates and saves a whole-Study summary'. The refresh/replace framing implicitly separates it from the read_study_summary sibling, but it never names the alternative, so differentiation is inferred rather than stated.

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?

'After explicit approval' gives a real precondition, and 'force regenerates unchanged coverage' implies when the force flag is warranted. However, no alternatives are named (e.g. read_study_summary for reading without regenerating) and no when-not-to-use guidance is offered.

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