get_canvas_ascii

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

With no annotations, the description carries the full burden. It discloses that output is characters only and no color info, which is useful. However, it fails to mention any side effects, authentication needs, rate limits, or performance characteristics. This partial disclosure is better than nothing but leaves gaps.

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 two short sentences with no unnecessary words. It efficiently conveys the core purpose and a primary use case.

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?

For a simple retrieval tool with no output schema, the description adequately indicates the return type (ASCII text). However, it does not explain the effect of parameters like trimEmpty or overlayPreviousFrame on the output, nor any performance implications. Given the parameter count and nested objects, slightly more detail would improve completeness.

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 coverage is 100%, so baseline is 3. The description does not add any extra meaning beyond what the schema already provides for the parameters (e.g., frameIndex, region, trimEmpty, overlayPreviousFrame). No additional details or examples are given.

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 verb ('Get'), resource ('canvas'), and output format ('raw ASCII text, characters only, no color info'), and distinguishes from siblings by highlighting it's for verifying visual appearance, as opposed to other get_canvas tools like get_canvas_preview or get_canvas_summary.

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 implies usage for verifying visual appearance, but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. This leaves the agent to infer context from the name and sibling list.

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