word_read_paragraph

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

Description implies read-only behavior ('Return') and lists common error conditions (invalid params, file not found, unsupported format). However, no explicit statement about being non-destructive, auth requirements, or side effects. Without annotations, this is adequate but not outstanding.

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?

Description is a concise docstring-style block with purpose, parameters, and error conditions. Every sentence adds value; no fluff. Front-loaded with the main action.

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?

Covers parameter semantics and error scenarios well. Missing explicit read-only declaration and usage guidance vs siblings, but output schema exists to handle return values. For a simple read tool, the description is largely 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?

Description fully explains each parameter beyond the schema: 'path' to an existing .docx, 'index' as zero-based, 'folder' as optional base folder. With 0% schema coverage, this compensates completely, giving clear semantics for correct invocation.

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 clearly states the tool returns a single paragraph's content and metadata. It specifies the resource (paragraph) by index, distinguishing it from word_list_paragraphs which lists all paragraphs. The verb 'Return' is specific and accurate.

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?

No guidance on when to use this tool versus alternatives like word_list_paragraphs or word_get_info. The description only lists parameters and errors, leaving the agent to infer usage context from tool names.

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