Convert Image to C Array for Hardware Displays

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

Annotations indicate readOnlyHint=false and openWorldHint=true. The description reveals behavioral details like rotation options and threshold for monochrome, but does not disclose potential side effects (e.g., writing output files, required permissions) or error conditions. Some value beyond annotations is added, but gaps remain.

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 relatively concise, using a bullet-like list for format types and parameter notes. It avoids unnecessary detail but could be streamlined further. The format is scannable, though the parameter list duplicates some info from the schema.

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?

With an output schema present, return values need not be explained, but the description still must cover all parameters and operational context. With 10 parameters, only 3 are partially described, leaving significant gaps. The tool's behavior for required fields like image_path and var_name is not addressed, making the description incomplete for effective use.

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 0% description coverage, placing full burden on the description. However, the description only explains 3 of 10 parameters (rotation, threshold, keep_aspect) with brief notes. Key parameters like image_path, width, height, var_name, and format_type remain unexplained, providing insufficient semantic context.

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 title and description clearly state the tool converts images to C arrays for hardware displays, listing supported color formats. It distinctly differs from sibling tools which are Arduino CLI commands and development utilities, leaving no ambiguity about its purpose.

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?

The description specifies the tool is for hardware displays (OLED, E-Paper, TFT, LEDs), providing clear context. While it does not explicitly mention when not to use it or name alternatives, the sibling set contains no other image conversion tools, making the usage scope unambiguous.

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