icon_set

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

With no annotations at all, the description carries the full burden and does so well: it discloses image transformation and resize, the on-disk location of written files, the external platform upload side effect, the required female and male slots, and an error code ICON_UPLOAD_FAILED with retry guidance. It leaves out whether existing icons are overwritten and what authentication the upload requires, which are the only notable side-effect 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 sentence begins with the purpose and the submission requirement, which is the right order. The parenthetical clauses pile up (提交窗口只认上传过的图标, 提交窗口要这两个), repeating the 'submission needs both icons' point more than once, but nothing is truly irrelevant.

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 four-parameter mutation tool with no annotations and no output schema, the description covers side effects, error handling, accepted image sources (generate_image output or capture_preview files), and the required follow-up call. Without an output schema, it could say what the call returns, and it says nothing about overwriting existing icons.

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 description coverage is 100%, so the schema already explains every parameter, including the type enum and the instance_id/project_path either-or rule. The description mostly restates the default for type (both slots) rather than adding new semantics, so baseline 3 applies.

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 names a specific verb and resource (设置特效图标), then enumerates the concrete operations: center-crop to square, scale to 360×360 PNG, write into the project's Icon/ directory, and upload to the Douyin effects platform. That is far more specific than the name alone, and the parenthetical (提交特效必需) distinguishes it from general icon-editing siblings such as icon_open.

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 clearly says when this tool is needed (submission requires uploaded icons) and ties it to the sibling workflow: the same files the 「图标制作」 window saves, the same effect as that window's 「完成」 button, plus the follow-up step with save_project. It does not state when to prefer icon_open or when not to use this tool, so the alternatives are only implied.

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