render_icon

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

Annotations only say readOnlyHint=false and destructiveHint=false, so the description adds value by disclosing that the tool saves output to the workspace and may return it inline. It also adds the environmental requirement of macOS with Icon Composer and the guarantee of no approximation or network fallback. It does not mention potential overwrite behavior or failure modes, but the added context is meaningful.

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?

Two sentences, front-loaded with the core purpose, and every sentence earns its place. The prerequisite and no-fallback caveat are stated compactly without padding.

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?

The tool has seven parameters, no output schema, and no parameter descriptions, yet the description only covers the general action, inline return, and a system requirement. It is not sufficient for an agent to know which parameters matter for a desired rendition, how tinting works, or what the rendered output/return payload looks like.

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 0% schema description coverage and seven parameters, the description should explain parameter meaning, but it only alludes to the inline concept. It does not clarify name validation, size range, rendition variants, tint controls, or opaqueBackground. The inline reference is minimal compensation for a large parameter surface.

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 clear verb (Render), a specific resource (Apple Icon Composer PNG appearance), and the key behaviors (save to workspace, optionally return inline). The phrase 'No approximation or network fallback' distinguishes it from sibling tools like create_icon or update_icon.

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?

It names an explicit prerequisite (macOS with Icon Composer) and implies a fallback unavailable, but it never says when to use this tool versus composer_status, create_icon, or list_icons. The usage context is implied rather than spelled out.

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