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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description's 'does not regenerate or replace' is largely a restatement of read-only behavior, adding only the mild signal that no regeneration compute/side effect is triggered; nothing about auth, limits, or output shape is added.

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?

Two short sentences with zero waste; the positive statement of what is read comes first and the negative constraint second. Every clause earns its place.

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 described, and the schema fully documents the single nested study parameter. The only meaningful gap is not explicitly routing the agent to refresh_study_summary for regeneration.

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 itself documents the id-over-name precedence and the omit-both-to-use-active-Study fallback. The description adds no parameter meaning beyond that, 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?

States a specific verb (reads) and resource (saved whole-Study summary), and enumerates the content returned: Markdown, evidence blocks, metadata. The negative clause 'does not regenerate or replace' implicitly separates it from the refresh_study_summary sibling, though that sibling is not named.

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 tool is only implicitly positioned: 'does not regenerate or replace' hints that regeneration is a different tool's job, but no condition, prerequisite, or alternative is stated explicitly. An agent must infer that refresh_study_summary is the counterpart.

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