get_docx_paragraphs

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

No annotations are provided, so the description must convey behavioral traits. It states the tool lists paragraphs with index and style, implying a read-only operation without side effects. However, it does not mention whether it modifies the file, requires specific permissions, or has limitations (e.g., performance on large files). The description is adequate but minimal.

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?

The description is a single, front-loaded sentence with no extraneous words. It efficiently communicates the action and output without filler.

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 the presence of an output schema (reducing the need to describe return values), the description covers the essential functionality. It could be enhanced by explicitly noting the tool is read-only or mentioning related tools like 'edit_docx_paragraph', but it is still sufficiently complete for a simple list operation.

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% with one parameter 'file_path' whose description ('Absolute path to the .docx file') is already clear. The tool description adds no additional semantic value beyond the schema, so the baseline score of 3 applies.

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 clearly states the tool lists all paragraphs from a DOCX file along with index and style. It uses a specific verb ('list') and resource ('paragraphs from a DOCX file'), effectively distinguishing it from sibling tools like 'get_docx_tables' or 'read_document'.

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 explicit guidance on when to use this tool versus alternatives such as 'read_document' or 'get_document_info'. The intended use case is implied by the tool name and description, but lacks context like 'use this to extract paragraph-level structure' or 'prefer this over read_document for structured access'.

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