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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral value by describing the tree's shape (origin node parentId=null, children along named axes) and the per-node attributes returned, which goes beyond the annotation set.

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?

Three tight sentences, front-loaded with the core payload ('One field's full tree'), followed by structural detail and the downstream-tool hint. No filler, though the parenthetical attribute list is slightly dense.

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?

No output schema exists, yet the description sketches the returned structure (nodes with id/parent/axis/description/pinned/color/image/desk-research flags plus AI-clustered groups) and how to use the results. Adequate for a read-only lookup, with minor gaps around grouping semantics.

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%: fieldId's origin (prism_fields_list) and the workspace/token rules are fully documented in the schema. The description adds no extra syntax or format detail for these parameters, so the schema carries the load — baseline 3.

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 (Read) and resource (one Prism field's full node tree), then enumerates what a node contains and adds the AI-clustered groups. This clearly distinguishes it from the sibling prism_fields_list (enumeration) and prism_fields_get (field metadata vs nodes).

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?

Gives forward-looking guidance: 'Use node ids with the expand / research / study tools,' and the schema notes the field id comes from prism_fields_list. It establishes the context and downstream workflow, though it never states explicit when-not conditions or names a directly competing read tool.

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