Update Document Icon

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

Annotations already convey mutation (readOnlyHint=false, idempotentHint=false). The description adds useful behavioral context: the icon slot is the 'sidebar icon' and that null removes it, which explains the mutation scope beyond the structured metadata.

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 primary purpose, then a succinct explanation of accepted inputs. 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?

With an output schema present and a simple parameter set, the description covers the core behavior and removal semantics. It omits any mention of the optional workspaceId parameter, but this is minor given the tool's simplicity and the presence of schema info.

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% and the description repeats what the schema already explains (emoji string, object, or null). It doesn't add meaning for the undocumented workspaceId parameter, so it only partially compensates for the coverage 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 'Set or clear the sidebar icon (the Notion-style emoji slot) on a document.' This is a specific verb+resource combination that distinguishes it from siblings like update_doc_title and update_folder_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?

The description gives clear context for the tool's scope ('on a document') and the ability to clear with null, which implies when to use. However, it doesn't explicitly mention alternatives or exclusions, like contrasting with update_folder_icon, so it misses a 5.

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