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

The annotations declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, which is surprising for a 'get' tool; the description does not explain this. It does add real behavioral context beyond the annotations: results are bounded excerpts, sequential reads are resumable via cursor, and a no-match must not be treated as verified evidence.

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 tight clauses with no filler, and the core behavior (bounded excerpts / continuable window) is front-loaded before the caveat. Efficient, though extremely terse for a 7-parameter 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?

An output schema exists and parameter coverage is high, so the description need not restate return values or parameter formats. What remains, mainly when to prefer each reading mode and the relationship to the search siblings, is only partially addressed, leaving a small gap.

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 86%, so the schema already documents query, cursor, source_id, source_type, and reading_mode semantics. The description adds essentially no parameter-level detail beyond the schema baseline, so 3 is the correct ceiling here.

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 operation on a resource: returning bounded source excerpts or a continuable sequential reading window. This distinguishes it implicitly from the search_* siblings (retrieval of evidence vs. discovery), though it never names those siblings explicitly, keeping it just short of a 5.

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?

Modes are implied (bounded excerpt search vs. continuable sequential reading), but there is no explicit statement of when to call this instead of search_filings/search_meetings/etc., nor prerequisites such as 'requires a source_id returned by a search tool'. Usage is inferable only from the schema.

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