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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, covering the safety profile. The description adds value by specifying the returned fields (title, question count, response count, open/closed), but says nothing about pagination, ordering, or authentication needs.

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 with zero filler. It immediately anchors the resource, scope, and returned fields, making it appropriately sized for a simple list tool.

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 three-parameter list tool with no output schema and annotations covering safety, the description is serviceable but incomplete. It lists returned fields but omits required-parameter semantics and pagination behavior, which an agent would need for reliable invocation.

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 only 33% (workspace is documented; fieldId and nodeId are not). The description implies nodeId through 'attached to one Prism node' but does not explain fieldId or compensate for the undocumented required parameters, leaving the agent to guess their role.

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 ('Feedback studies') and scopes it to 'one Prism node', and lists returned fields. This distinctively separates it from the workspace-level sibling (prism_studies_list_workspace), but the description itself lacks an explicit verb and relies on the title ('List') to convey the action.

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?

There is no explicit when-to-use or when-not-to-use guidance. The scope 'one Prism node' implies the required context, but no alternatives or prerequisites are named, and no routing advice is given relative to prism_studies_list_workspace or other study tools.

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