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

Annotations only declare destructive/openWorld/not-readOnly; the description adds substantive behavior well beyond them — publish is one-way and starts working the participant link, questions is a whole-replacement that is LOCKED once responses exist (server refuses with `invalid`), null semantics for endChatFocus/completionRedirectUrl/autoAnalyzeTarget, and the possible `needs_confirmation` return. This is rich operational context.

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?

Front-loads the publish semantics and then moves through the edit surface efficiently; nearly every clause carries information. The dense parentheticals make it slightly hard to scan but nothing is gratuitous.

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?

For a 12-parameter, multi-purpose mutation tool with no output schema, the description covers the impactful fields and the locking/confirmation behaviors an agent must know. Coverage of workspace and approvalId is thin, but the structured schema fills that gap, keeping it close to complete.

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?

With only 33% schema description coverage, the description carries much of the load and does so well: it explains what questions replaces, that it needs prism_studies_get for shape, the null-clears behavior for several fields, and endChatEnabled+endChatFocus pairing. It leaves workspace/approvalId unexplained, but workspace is covered by the schema itself.

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 the resource (a study) and enumerates the concrete mutations it performs: publish, close/open, edit title, replace questions, set adaptive follow-ups, closing chat, redirect URL, and auto-analyze target. It also routes the agent by naming siblings prism_studies_get and prism_studies_list_workspace, so it is distinguishable from the read/list tools.

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 real when-to-use guidance: 'read prism_studies_get first', the LOCKED-once-responses rule with the explicit answer 'a new study', and where ids come from (prism_studies_list_workspace). It does not, however, contrast this with prism_studies_draft or explicitly state when not to use update at all, so it stops short of the top tier.

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