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

Annotations indicate this is not read-only (readOnlyHint false) and not destructive (destructiveHint false), but the description adds no details about side effects, idempotency, or potential failures. It does not disclose whether renaming affects child folders or if moving changes hierarchy in any other way.

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 a single, concise sentence that fits the essential information without fluff. It is front-loaded with the primary action and directly states what the tool does.

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 the simple parameter set and lack of an output schema, the description is sufficient for an agent to understand the operation's purpose and invocation. No additional context is required for this straightforward update action.

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?

All parameters are documented with clear semantic meaning. 'name' is described as 'New folder name', 'parent_folder_id' explains the null case for moving to root, and 'folder_id' is clearly the unique identifier. Schema coverage is 100%.

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 a specific action ('Rename' or 'move') on a specific resource ('agent folder'), distinguishing it from sibling create/delete/list operations. It conveys the exact scope of the operation without ambiguity.

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 implies usage for modifying an existing folder but does not explicitly mention when to prefer this over creating, deleting, or moving multiple folders. Alternatives like 'moveAgentsToFolder' are not referenced, leaving some room for interpretation.

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