test_case_folders_update

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

With no annotations, the description carries full burden. It discloses important behavior: changing parentId moves the entire subtree and hierarchy depth is limited to 3 levels or rejected with 400. However, it does not mention idempotency, side effects, permissions, or what happens on partial updates.

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 concise with two main parts: a clear action statement and a behavioral note. The 'Tag: Test Case Folders' line is redundant and slightly detracts from conciseness, but overall it is well-structured and front-loaded.

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 and 4 parameters, the description lacks key information: return value (e.g., the updated folder), idempotency, effect of partial updates (only name or order), and any prerequisites or permissions. The subtree move behavior is detailed, but essential context for tool usage is missing.

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 low (25% with only id described). The description adds context for parentId (subtree move, depth limit) but does not explain name, order, or id beyond what schema provides. This partially compensates for the low coverage.

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 'Update test case folder' as the action, which is a specific verb+resource. It distinguishes from siblings like create/delete/list by focusing on updating existing folders and adds unique behavior about moving subtrees when parentId changes.

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 does not explicitly state when to use this tool vs alternatives like test_case_folders_create or test_case_folders_list. It implies usage for updating a folder's name/order/parent but lacks clear guidance on when not to use it or what to use instead.

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