Get CoDesign Artboard Image

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

Discloses that download=true stores the image under a specific path and gives selector precedence, but lacks details on error handling or other behaviors. With no annotations, it carries burden well.

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?

Four sentences, front-loaded purpose, no redundancy, every sentence adds value.

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?

Covers purpose, guidelines, and key behaviors but omits parameter details, return type, and error scenarios. Adequate but gaps exist.

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 0%, so description should compensate. It gives selector precedence and mentions download effect, but leaves many parameters (password, sharingUrl format, etc.) unexplained.

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 it returns the CoDesign preview/cover image for visual comparison only, and distinguishes from sibling tools by recommending get_artboard_spec and download_slice for implementation.

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?

Explicitly states when to use (visual comparison) and when not to (do not crop for production slices), and names alternatives (get_artboard_spec, download_slice).

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