Update Folder Icon

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

Annotations declare this as a write operation (readOnlyHint=false) and not destructive. The description adds 'Experimental' as a behavioral note, but does not disclose side effects, error behavior, or permission requirements beyond what annotations already provide.

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 two sentences, front-loaded with the core action, and each sentence adds value. No wasted words.

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 3-parameter write tool with annotations and no output schema, the description is adequate but not comprehensive. It lacks mention of return values, error cases, or permission context, though the experimental tag adds minimal context.

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 67% (workspaceId missing description). The description clarifies icon parameter types (emoji string, object, null) somewhat, but the schema already describes the anyOf variants. It does not compensate for the undocumented workspaceId parameter, leaving a gap.

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 action: 'Set or clear the sidebar icon on an organize folder.' It specifies the possible inputs (emoji string, icon object, null) and distinguishes from sibling tools like get_folder_icon (read) and update_doc_icon (different resource).

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 implies usage for updating folder icons but does not provide explicit when-to-use or when-not-to-use guidance relative to siblings. The 'Experimental' note hints at caution but lacks alternatives or exclusions.

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