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

Annotations already declare the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description earns credit by disclosing the scope filter ('every study with responses') and the payload shape, including the non-obvious 'origin' taxonomy (standalone / canvas node / tracker wave) and the Ledger-kept insight field — details the 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?

Two sentences, front-loaded with the payload enumeration and closing with the routing advice. The field list is long but justified because there is no output schema; nothing is wasted, though the enumeration could be tightened slightly.

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?

With no output schema, the description carries the burden of describing return values and does so thoroughly. Remaining gaps are minor: no mention of ordering, pagination, or size/limit behavior for workspaces with many studies, and no note on behavior when a workspace has zero studies with responses.

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?

There is one parameter and schema description coverage is 100%, so the schema already explains that workspace is required for personal tokens with no default and ignored for workspace API keys. The description adds nothing about this parameter, so the baseline 3 for a fully-documented single-param tool is appropriate.

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 names a specific artifact ('a cross-study digest') and enumerates exactly what it contains — every study with responses, title, origin, response count, latest analysis summary, top themes, and Ledger-kept insights. It routes distinctly away from siblings by pointing to prism_studies_get and prism_studies_results for follow-up, so an agent can tell it apart from prism_studies_list without opening a schema.

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 states the triggering scenario ('The starting point for "what have we learned about X?"') and names two concrete follow-up alternatives with the object they act on. It stops short of saying when NOT to use it — notably it never distinguishes itself from the sibling research_findings_list or prism_studies_list_workspace, which a naive agent might otherwise reach for.

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