GenOffice docx blocks

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

No annotations are provided, so the description carries the burden. It discloses that it lists top-level blocks (and not deeper nesting) which is useful, but does not state error behavior for invalid paths, file-size limits, or whether it only handles paragraphs/headings/tables. No contradiction present, adds modest context about scope.

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 tight sentences with zero waste. The first states the operation and output; the second gives actionable placement guidance. Every word earns its place.

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 simple single-parameter read tool with 100% schema coverage, the description is complete: it states the operation, the output shape (index/type/style/text), and the intended workflow. It doesn't discuss pagination or large-file behavior, but given the simplicity this is sufficient.

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 only one parameter (path), fully described as 'Absolute path to the .docx file.' The description confirms it operates on .docx files but adds no additional format or constraint detail beyond the schema.

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?

Specific verb+resource (Parse a .docx with the GenOffice engine) and clearly lists the output (top-level blocks with index, type, style, text). Distinguishes from siblings by naming genoffice_docx_patch as its downstream counterpart.

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?

Explicit when-to-use guidance: 'Use this BEFORE genoffice_docx_patch to pick the block indexes you want to rewrite.' This clearly positions it as a prerequisite step and names the alternative/successor tool.

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