Create ASCII render

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

Annotations already indicate readOnlyHint=false, and the description adds meaningful detail by specifying that it creates a new baseCOMP containing resolutionTOP, textTOP, glslTOP, and nullTOP, plus exposed controls. This goes beyond the structured annotations while remaining consistent with them.

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 three sentences, front-loaded with the core purpose, and each sentence contributes unique information: algorithm, modes/aesthetic, and output structure/controls. No redundant or filler content.

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 (11 params, no output schema), the description offers a solid overview: what it does, how it works, what it creates, and key controls. The schema covers all parameters with descriptions. It doesn't mention limitations or prerequisites, but the source-optional fallback is captured in the schema, so the description is sufficiently complete for selection and invocation.

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?

With 100% schema coverage, the baseline is 3. The description enhances parameter understanding by explaining the luminance quantization grid (connecting resolution and cell_size), the color modes (aligning with color_mode), and the glyph atlas (relating to charset/font). This adds conceptual clarity beyond the schema descriptions.

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 states a specific verb ('Turn any TOP') and resource ('into a character-grid ASCII render'), clearly distinguishing it from other create_* siblings like create_halftone. It also details the algorithmic process and outputs, leaving no ambiguity about the tool's function.

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 clearly implies when to use the tool: whenever an ASCII/character-grid render of a TOP is needed. It provides context about supported modes and default aesthetic, but does not explicitly name alternatives or exclusion criteria, so it falls short of a 5.

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