get_selection_as_image

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the output (PNG image) and acknowledges it's a placeholder, but lacks details on side effects, permissions, or whether it is read-only.

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 with two sentences: the first clearly states the tool's purpose, and the second adds useful context about its placeholder status. Every sentence is necessary and front-loaded.

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 low complexity (no parameters, no output schema), the description adequately covers the tool's purpose and current limitation. However, it could mention the return format in more detail (e.g., resolution, encoding).

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 tool has no parameters, and the baseline score for 0 parameters is 4. The description does not need to add parameter semantics, so it adequately fulfills this dimension.

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 returns a visual representation of currently selected Sketch layers as a PNG image. It is a specific verb+resource combination that distinguishes it from sibling tool run_code.

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 includes a hint that the tool is a placeholder and suggests re-fetching after Sketch is started, but it does not provide explicit guidance on when to use this tool versus the sibling tool run_code, nor does it mention conditions for use.

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