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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered externally. The description adds that this is a node-scoped read returning summary fields, but says nothing about ordering, pagination, or what an empty result means. Adequate given the annotation coverage, not rich.

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?

A single front-loaded sentence fragment with no filler; the scope comes first and the returned fields second. It is appropriately sized for a simple list tool, though the fragment style leaves no room for the usage signal the tool needs.

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 usefully compensates by naming the returned fields. However, for a 3-parameter tool with two required, undocumented identifiers and no mention of pagination or result limits, the definition is only minimally 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?

Schema coverage is only 33%: only 'workspace' carries a description (default-workspace override rules), while nodeId and fieldId are bare strings. The description hints at nodeId via 'one Prism node' but never explains what fieldId is or why both are required, so it does not compensate for the coverage gap.

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 verb (list) and resource (feedback studies) and scopes it to 'one Prism node', which separates it in spirit from the workspace-wide sibling. It also enumerates the fields returned (title, question count, response count, open/closed), so the agent knows what it gets. It stops short of naming prism_studies_list_workspace as the alternative.

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?

'Attached to one Prism node' implies the usage context (fetch studies for a specific node rather than workspace-wide), but there is no explicit when-to-use, when-not-to-use, or named alternative despite prism_studies_list_workspace and prism_studies_get existing as plausible siblings. Usage is inferable but not stated.

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