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

Annotations already declare readOnlyHint, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds real behavioral value by describing the tool as a cross-study rollup and listing the fields it surfaces, letting an agent predict the payload. It stops short of noting pagination or size limits, which keeps it from 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?

Two sentences, no waste. The content of the digest is front-loaded in a scannable list, and the usage/routing sentence follows. 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?

There is no output schema, and the description compensates by enumerating the return fields in detail, which is exactly what an agent needs to know before calling. Purpose, usage, and follow-up routing are all present for a simple read-only tool.

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 single 'workspace' parameter is fully documented there, including token/default-workspace behavior. The description never mentions the parameter, so it adds nothing beyond the schema — the baseline 3 for full schema coverage.

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 resource and scope: a cross-study digest covering 'every study with responses,' and enumerates exactly what it includes (title, origin, response count, latest analysis summary, top themes, Ledger insights). It also distinguishes itself from siblings by naming prism_studies_get and prism_studies_results as follow-ups rather than competitors.

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?

Explicitly positions itself as 'the starting point for "what have we learned about X?"' and directs the agent to specific alternatives (prism_studies_get for insights, prism_studies_results for details) on the studies that matter. The when-to-use and when-to-escalate conditions are both spelled out.

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