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

Beyond the annotations, the description discloses exactly what is destroyed: the saved summary is replaced without restore history while questions and answers remain. It also explains the background/pending receipt behavior and the force condition, which are important behavioral details for a destructive async operation.

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 front-loaded with the action and approval requirement, then covers destruction, force, and return behavior in compact sentences. Every clause adds useful information without repetition.

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, asynchronous, nested-parameter tool with annotations and an output schema, the description covers approval, destruction scope, force behavior, and pending receipts well. It is slightly incomplete on study selection and length semantics, but those are partly covered by the schema.

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 75%, so the schema already documents most parameters. The description reinforces force and approval semantics but does not add meaning for the study id/name selection or the length enum beyond what the schema 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 states a specific verb and resource: it refreshes a whole-Study summary. It makes the scope clear through 'whole-Study summary refresh' and distinguishes refresh from read by describing replacement behavior, but it does not explicitly name the sibling read_study_summary.

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 a clear prerequisite: an explicit approval is required, and it explains that force is for unchanged coverage. However, it does not say when to use this instead of read_study_summary or other study tools, and it gives no explicit when-not guidance.

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