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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real value beyond that by disclosing the return content (study list with response/theme counts, desk-research presence) and a scope change note that interviews have moved to study level. It doesn't cover auth/limits, but for a read tool this is solid.

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 purpose is front-loaded in the first clause, followed by return contents and then routing guidance. The parenthetical asides are terse and each sentence carries distinct information (what it returns, the interview exception, when to reach for it). No filler.

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?

There is no output schema, so the description must convey returns — and it does, listing the study-level counts and desk-research flag. Combined with annotations covering the read-only profile, an agent has enough to call it correctly, though pagination or full result shape is not described.

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%, so the baseline is 3. The description adds meaning to the subjectType enum by clarifying it is 'today: a Prism node,' explaining why the enum has a single value and hinting at future expansion. It adds little for subjectId and workspace, but the schema already documents those.

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 verb+resource ('Cross-instrument findings for one subject') and enumerates exactly what is returned: attached feedback studies with response counts + theme counts, and desk-research existence. It also distinguishes itself from the sibling prism_interviews_list by stating interviews are now study-level. An agent can tell what this does and how it differs from neighbors 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?

Explicit when-to-use guidance is provided ('THE PLACE TO LOOK before proposing new research: cite what already exists') and a concrete alternative is named for the interview case ('read them per study with prism_interviews_list'). It lacks a general when-not clause, but the routing intent is clear.

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