grabzit_convert_html

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

With no annotations, the description carries full burden but only states the basic conversion. It doesn't disclose behaviors like default format ('jpg'), delay handling, or possible limitations (e.g., output file type). Additionally, there is an internal inconsistency: description says 'raw HTML string' while schema says the 'html' parameter expects a URL.

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 filler. Every word contributes to stating the core function.

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?

The tool has 7 parameters, 3 enums, and no output schema, but the description is too minimal to guide correct invocation. It doesn't mention key parameters, return behavior, or how to choose between output formats. A more detailed description is needed given the tool's complexity.

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 description coverage is 100%, so baseline is 3, but the description introduces ambiguity by calling input 'raw HTML string' while the schema says it's a URL. This contradicts the parameter description and reduces clarity rather than adding value.

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 a specific verb ('Converts') and resource ('raw HTML string') with target formats ('Image, PDF, or DOCX'). It distinguishes from sibling tools like grabzit_convert_url by emphasizing raw HTML string input, though it doesn't explicitly compare to siblings.

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 grabzit_convert_url or grabzit_scrape_html. The description implies usage for HTML string input but provides no context or exclusions.

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