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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is carried by structured data. The description adds the useful distinction between the two mutation modes (rename vs. move) but says nothing about side effects of moving, permission requirements, or reversibility.

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?

A single front-loaded sentence with zero filler; both supported operations are stated up front and nothing is wasted.

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 three-parameter mutation whose annotations already cover the destructive/idempotency profile and whose schema is fully documented, the description is nearly sufficient. The only real gap is not clarifying that supplying neither name nor parent_folder_id results in a no-op.

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 100%, so name, folder_id, and parent_folder_id are already documented, including the null-to-root behavior. The description only restates the rename/move mapping to those parameters, adding no syntax or edge-case detail beyond the schema.

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?

States a specific verb+resource with the two supported operations ('rename an agent folder or move it to a new parent'), which cleanly separates it from createAgentFolder, deleteAgentFolder, and listAgentFolders. It does not explicitly contrast with the similarly-named moveAgentsToFolder or moveAutomationsToFolder siblings, but the resource is 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?

Usage is implied by the operation itself, but there is no explicit when-to-use, no prerequisites, and no routing guidance against siblings like moveAgent or moveAgentsToFolder. It also fails to note that at least one of name/parent_folder_id must be supplied, since only folder_id is required.

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