read_document

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

No annotations provided; description states only that it reads plain text. Does not disclose encoding, size limits, error handling, or whether the file is read-only (though that is implied). Minimal behavioral context beyond the obvious.

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?

Single sentence is concise but lacks any structure or additional context. While no waste, it is under-specified for a tool with no annotations or output schema.

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?

Given simple tool with one parameter and no output schema, the description is minimally adequate but missing return format, error behavior, and supported document types. Not fully complete.

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 has 0% description coverage and description adds no meaning to the 'filePath' parameter (e.g., no format, absolute/relative hint, supported file types). The parameter remains unexplained.

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?

Description uses specific verb 'read' and resource 'Word document's plain text content', clearly distinguishing from sibling tools 'append_document' and 'create_document' which modify rather than fetch content.

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?

Implied usage: use when needing to extract text from a Word document. No explicit when-not or alternatives are given, but siblings provide contrast.

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