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

Annotations already cover safety (readOnlyHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real value beyond them: result ordering, the exact fields returned, and the status vocabulary (running / ready / failed).

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 filler: the first front-loads scope, ordering and returned fields; the second handles the handoff to the sibling tool. Every clause carries information.

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 usefully enumerates the returned fields and status values, which is the main thing an agent needs. It is close to complete for a simple list tool; only the required studyId identifier goes unexplained.

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 coverage is 50%: the workspace slug is well documented in the schema, but the required studyId has no description anywhere. The prose mentions no parameters at all, so it neither compensates for the studyId gap nor adds format/syntax detail beyond what the schema already gives.

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?

Specific verb (list) plus resource (desk-research reports on a study) with an explicit ordering guarantee ('newest first'). It names the sibling it complements, prism_research_reports_get, so an agent can distinguish listing from fetching 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?

Explicitly routes the agent: use this to enumerate reports, use prism_research_reports_get to 'read one in full'. The when-to-use alternative is clear, though there are no stated exclusions or preconditions (e.g. what happens with no reports or no studyId).

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