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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses the returned data shape (id, parent, axis, description, pinned, color, image/desk research), the AI-clustered groups, and the data model detail that the origin node has parentId=null. That is useful structural context with no output schema present.

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 compact sentences, front-loaded with the resource and contents, followed by a practical pointer to downstream tools. Every clause carries information with no padding.

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 carries the burden of explaining return values and does so thoroughly. Combined with readOnly annotations covering safety and the schema covering parameters, an agent has what it needs to call this correctly.

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%, so both fieldId and workspace are already documented in the schema, including the workspace-token nuance. The description adds only incidental meaning (node ids) and does not expand on parameter semantics. Baseline 3 applies.

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 states a specific resource (one field's full node tree) and enumerates its contents, distinguishing it from prism_fields_list and the node-level tools. It falls just short of explicitly naming which sibling it complements at the start, but the picture is clear.

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 hints at the workflow by saying 'Use node ids with the expand / research / study tools,' implying this is a discovery step, but never states when to prefer this over prism_fields_list or prism_nodes_expand. Usage is implied rather than explicit.

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