Get Folder Icon

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds that it returns null when no icon is set and marks the tool as 'Experimental,' providing useful behavioral context beyond the annotations.

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 extremely concise with two sentences, no filler, and front-loaded with the core purpose. Every sentence adds value: the first states the action, the second gives return behavior and experimental status.

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 simple read tool with no output schema, the description covers the basic functionality (reading icon, null return) and the experimental tag. However, it could specify the format or type of the returned icon (e.g., URL or path) to be fully complete.

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 50%: only 'folderId' has a description. The description does not add meaning for 'workspaceId' (undocumented). The description mentions 'sidebar icon of an organize folder' which implies the folder is identified, but does not clarify the role of workspaceId.

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 tool reads the sidebar icon of an organize folder and specifies the return behavior when none is set. The verb 'Read' and resource 'sidebar icon of an organize folder' are specific and distinct from sibling tools like 'update_folder_icon' or 'get_doc_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?

No guidance on when to use this tool versus alternatives is provided. It does not mention prerequisites, context, or when not to use it (e.g., if the icon is not set, it returns null but doesn't advise checking null). No sibling differentiation is discussed.

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