Convert a local image to ASCII art

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

With no annotations provided, the description carries the full burden. It does disclose two safety behaviors: paths and numeric arguments are bounded, and existing outputs are never overwritten. However, it does not mention error handling, permissions, side effects, or what happens on invalid input. While it provides some useful guarantees, it is not comprehensive for a tool that creates files.

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 concise: two short sentences, front-loaded with the core action. It contains zero fluff and efficiently communicates the main purpose and two key constraints.

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 tool's complexity (8 parameters, no output schema), the description is severely incomplete. It fails to explain parameter meanings, expected output content, error behavior, or any example usage. An agent would not be able to call this tool correctly without additional information or external knowledge.

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 0%, so the description must compensate, but it does not explain any of the 8 parameters (mode, trim, width, height, invert, threshold, input, output). The generic note that 'numeric arguments are bounded' adds no meaning to individual parameters. An agent cannot infer the semantics of 'trim' or 'threshold' from this description, making it critically inadequate.

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 converts an absolute local PNG or SVG to a new .txt file, specifying input formats and output type. It is unambiguous about the primary function and distinguishes itself from any potential sibling by the resource (image) and output (.txt).

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 gives no explicit guidance on when to use this tool versus alternatives, nor does it mention any conditions or exclusions. It implies usage for local images but does not address scenarios like remote images or other conversion tools. There is no 'when to use' or 'when not to use' context.

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