update_folder

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

The description discloses the side effect that hiding a folder hides its contents. The annotation destructiveHint=true is consistent with that side effect, though other potential side effects (e.g., moving affecting child paths) are not mentioned.

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: first lists the actions, second explains partial update and the hiding side effect. No unnecessary detail.

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 description is sufficient to distinguish from sibling tools and provides the key behaviors needed to call it. It does not mention the return value or error conditions, but that's minor given the absence of an output schema.

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 descriptions cover id, hidden, and parent, but label and favorite lack descriptions. The tool description provides some context for these (rename, favorite state), but the semantics are not fully detailed.

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 that the tool renames, moves, toggles favorite/hidden state, and specifies that it operates by id. This distinguishes it from create/delete/restore folders.

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 explains partial update behavior (fields not passed keep current value) and notes the side effect of hiding contents. While it doesn't explicitly mention alternatives, the sibling tools are distinct enough that an agent would know when to use this for modifications.

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