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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them. It goes further by disclosing default full-document behavior, chunked reads, and SHA-256 local verification, plus the explicit no-side-effect guarantee — meaningful behavioral context beyond the annotations.

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 dense sentences, front-loaded with the core action and scope; the second sentence efficiently packs chunking, verification, and side-effect guarantees with no filler or repetition.

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?

An output schema exists, so return-value detail is out of scope for the description. It covers default behavior, chunking, verification, and side effects adequately; the only real gap is explicit pagination guidance for limit/offset, which the low schema coverage leaves for the description to fill.

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% (limit and offset are bare). The description hints at pagination via 'bounded chunks' and implies default returns everything, but never explains how limit/offset combine, max sizes, or the SHA-256 mechanism. It partially compensates but leaves the two undocumented parameters under-explained.

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 (published usage terms) and sharpens scope with 'COMPLETE... not a summary', so the agent knows exactly what it gets back. No sibling among the eclypse_* session/account tools competes for this function, so no differentiation is needed.

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?

Clearly frames the context in which this is the right tool — reading full terms without an account or browser — and rules out side effects ('never accepts terms, registers an account or authorizes payment'). It does not name an alternative or state when NOT to use it, so it falls short of a 5.

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