Download CoDesign Slice

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

Annotations indicate readOnlyHint=false (side effects) and idempotentHint=true. Description adds context: downloading and saving local files under a specific path, which is a side effect but not destructive. It does not contradict annotations and provides additional behavioral insight (e.g., local artifact creation).

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?

Three concise sentences: first states action and source, second provides usage guidance, third describes output and filters. No redundant content; information is front-loaded and efficient.

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 8 parameters and no output schema, the description covers main purpose, usage, output location, and filters. It lacks detail on some parameters (e.g., password, screenId) but is sufficient for an agent to use the tool correctly with contextual understanding from sibling tools.

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 38%, meaning only 3 of 8 parameters have schema descriptions. The description explains layerObjectId, format, and scales, but does not cover sharingUrl, password, screenId, etc. It adds value for key parameters but leaves gaps for others.

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 downloads CoDesign slice assets, specifies the source (official slice manifest), matching method (layer object_id), and output location (local paths). It distinguishes itself from alternatives like Python/PIL or screenshot cropping, making its purpose very clear.

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 says 'Use this for implementation assets instead of using Python/PIL or screenshot cropping,' providing a clear directive on when to use this tool versus alternatives. Also mentions optional filters, further guiding correct invocation.

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