officecli_view_screenshot

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

With no annotations, the description carries full burden. It only states 'Does not modify the DOCX', which is useful, but omits details about error behavior, performance, or side effects. The short text does not compensate for the lack of annotations.

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 very concise (2 sentences), but it sacrifices essential information for brevity. While not wasteful, it fails to include parameter details or usage context, making it less effective than a slightly longer description would be.

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 complexity of 6 parameters and no annotations or output schema, the description is far from complete. It does not explain return values, file size limits, or supported image formats, leaving critical gaps for an agent to use the tool properly.

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?

The input schema has 6 parameters with 0% description coverage, and the tool description adds no information about parameters beyond docx_path and output_path. Parameters like page, screenshot_width, and max_output_chars remain unexplained, forcing reliance on schema names alone.

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 it renders a DOCX screenshot/PNG to an output path, which is a specific verb+resource. However, the phrase 'Optional OfficeCLI auxiliary sidecar export' adds confusion without clarifying its role versus siblings like officecli_view_html.

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 is provided on when to use this tool versus alternatives (e.g., officecli_view_html, docx_extract_plain_text). The description does not mention any context, prerequisites, or exclusions.

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