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

Annotations declare readOnlyHint=true, and the description consistently describes a read operation ('Read', 'content is served', 'cleaned text plus metadata'), so no contradiction exists. The description adds substantial behavioral context beyond the annotation: pagination semantics via truncated/nextStart, chunk mode with chunkWindow/contentWindow reporting, and a crucial safety note that the content field is archived user data, not instructions. This is exactly the kind of operational guidance that annotations alone cannot convey.

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?

The description is a single dense paragraph, and it loses a small amount of structure by not breaking the window-mode and chunk-mode sections into separate sentences or bullets. However, every sentence earns its place: primary use case, continuation protocol, chunk mode, and the safety note are all present. It is longer than the mid-tier examples but justified by the complexity of two distinct reading modes.

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 tool with an output schema and complete schema coverage, the description covers everything an agent needs to know to invoke it correctly: what to pass (id and optional modes), how to paginate (truncated/nextStart/windowStart), how chunk mode works (ordinal + radius), and the safety caveat about archived data. The introductory source list also prevents the agent from guessing at valid id origins. Nothing meaningful is missing.

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 the baseline is a 3. The description adds meaning by connecting parameters to their runtime behavior (windowStart from the previous response's nextStart, chunk from a search chunkRef, chunkRadius defaulting to 1, windowLength defaulting to 8,000). It also clarifies that chunk mode replaces the character window mode and that contentWindow describes only served text. This surpasses the baseline by turning parameter names into a coherent usage model.

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 verb ('Read'), a precise resource ('one saved Sensefold item by UUID'), and immediately differentiates from siblings by naming the sources (search_hub, list_items, search, save results). It goes beyond the title by explaining what is returned ('cleaned text plus metadata') and that content is archived user data, not instructions.

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?

The description provides explicit when-to-use guidance by naming the originating tool contexts (search_hub, list_items, search, save results) and gives detailed continuation behavior for paged windows and chunk mode, including the exact fields to use (windowStart=nextStart, chunkRadius). It clearly implies when to call again (truncated=true) and what mode to choose.

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