edit_folder

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

The annotation destructiveHint=true already indicates the tool modifies state. The description adds the specific behavior of moving to root via empty string. However, it does not disclose potential side effects like cascading moves, permission requirements, or error conditions. This is adequate but not rich.

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?

Single sentence with two clear clauses, zero wasted words. Front-loads the primary actions and includes a crucial edge case. Perfectly concise for the information conveyed.

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?

Given no output schema, the description covers the core behaviors (rename and move) and a key edge case (empty string for root). It lacks mention of return value, error handling, or permissions, but for a mutation tool with good parameter documentation and annotations, this is sufficient for an agent to invoke correctly.

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 100%, so the baseline is 3. The description adds a summary of the two actions and repeats the empty string behavior already documented in the schema. It does not introduce new semantic meaning beyond the schema, maintaining the baseline.

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 explicitly names two specific actions ('rename' and 'move') on the 'folder' resource, clearly distinguishing it from sibling tools like add_folder, remove_folder, and list_folders. The verb+resource pair is precise and unambiguous.

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 clearly states when to use the tool (to rename or move a folder) and provides a special case for moving to root with an empty string. While it doesn't explicitly exclude alternatives, the sibling tools have distinct purposes (add, remove, list), making the context clear enough for selection.

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