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

Annotations declare readOnlyHint=false and destructiveHint=true, and the description backs that up concretely rather than contradicting it: it discloses that reads can queue recovery and overwrite stale/missing derived summaries, and bounds the blast radius with 'never reruns respondents'. What it omits is when the overwrite actually triggers and whether any permission is required.

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 tight sentences, front-loaded with the return payload before the side-effect caveats. Dense but every clause carries information; only 'refresh receipt' and 'respondents' assume internal vocabulary an agent may not share.

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?

An output schema exists, so return values need not be spelled out, and the description covers the surprising part of this tool: that a nominally read operation can mutate derived state. The remaining gap is routing relative to refresh_study_summary, which matters because both tools appear to touch summary freshness.

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%, and the schema already explains id precedence over name and the omit-to-use-active-Study behavior. The description adds nothing about how the study reference affects behavior (e.g. whether a name lookup can be ambiguous), so the baseline 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 uses a specific verb ('Returns') and enumerates the exact payload: whole-Study Markdown, evidence, generation state and the caller's refresh receipt. That is far more precise than the name alone. However, it never distinguishes this tool from the sibling refresh_study_summary, whose territory ('queue recovery and overwrite stale/missing derived summaries') this description partially claims.

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?

Usage is only implied: read the saved summary, and use it when derived summaries are stale or missing so recovery can be queued. There is no explicit when-to-use / when-not statement and no pointer to refresh_study_summary or render_study_results as alternatives, which is a real risk given how closely this overlaps with a refresh tool.

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