Read Filing Lines

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

Beyond the readOnlyHint annotation, the description discloses the 2,000-line return cap and the truncation/continuation behavior (next startLine), which the annotation does not carry. It adds useful operational context, though it does not detail error handling or how the 'next startLine' is surfaced.

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 action and followed by usage and output behavior. No filler or redundancy.

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 read-only tool with a fully covered schema and no output schema, the description supplies what an agent needs: the resource, how to obtain inputs, and the return-size/continuation model. Nothing material 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 all three parameters (documentId, startLine, endLine) are already fully documented, including 1-based inclusive semantics and the truncation note. The description reinforces the range/limit concept but adds little beyond what the schema already provides.

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 (numbered lines from an SEC filing or earnings-call transcript), and implicitly contrasts itself with SearchDocument, which produces the line numbers rather than reading them. An agent can distinguish this from its siblings without opening the schema.

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?

Provides clear workflow context by naming SearchDocument as the source of line numbers and offering the alternative of requesting a known range. It stops short of explicit when-not-to-use guidance or edge cases, but the intended entry point is unambiguous.

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