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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description earns credit by disclosing state semantics beyond the annotations: insights.activeRun signals an in-flight analysis that must be awaited, and participantUrl is only present when the study is open and a link has been minted. It says nothing about auth/permissions or pagination, so not a 5.

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 dense but purposeful sentences, front-loaded with the returned payload before the state caveats. Every clause carries information; the parenthetical about activeRun is slightly heavy but justified.

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 carries the burden of describing the return shape, and it does so thoroughly (fields, state, analysis, share link). The main remaining gap is the absence of any guidance on obtaining a studyId or the workspace requirement, which an agent needs before calling.

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?

Only 50% of parameters carry schema descriptions, and the description contributes nothing about either parameter. studyId is undocumented in both schema and description, and workspace (which has schema text) is not clarified further. With the coverage gap on the required identifier, the description fails to compensate.

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 resource (one study) and enumerates exactly what it returns: questions, response count, open/closed state, stored analysis, and participantUrl. That is far more specific than a generic 'get a study'. It doesn't explicitly differentiate itself from close siblings like prism_studies_results or prism_studies_report, which keeps it just short of a 5.

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 operational guidance ('wait for it before citing' when activeRun is set, 'cite theme strengths when reporting results'), which implies usage context. However, it never states when to reach for this tool versus prism_studies_list, prism_studies_results, or prism_studies_analyze, so the routing decision is left to inference.

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