docread

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

Discloses output section formatting and auto-truncation at 40000 chars. No annotations provided, so description carries burden. Missing details on error handling or performance, but key behaviors are covered.

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 sentences, first lists formats efficiently, second explains output format and truncation. Slightly dense but every word adds value. No 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?

With output schema present, return values need no extra description. Covers truncation and section formatting. Lacks info on file size limits or required permissions, but sufficient for typical use.

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 100%, but description adds significant value for 'range' parameter by detailing format per file type (PDF, PPTX, etc.). 'filepath' is straightforward. Enhances schema meaningfully.

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?

Clearly states the tool reads and extracts text from document files, listing multiple supported formats. Differentiates from sibling 'docgrep' which likely searches within documents.

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?

Implicitly clear this is for reading full text; sibling 'docgrep' suggests a search tool. Lacks explicit when-not-to-use but context provides sufficient differentiation.

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