test_case_folders_create

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals one important behavior: creating a folder beyond the third sub-level results in a 400 error. However, it does not disclose other behaviors such as whether creation is idempotent, what happens on success (response details), or how the 'order' parameter affects folder positioning.

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 substantive sentences. However, it includes a 'Tag: Test Case Folders' line that does not add functional value. The structure front-loads the purpose, which is good, but the tag breaks the flow and wastes characters. Overall, it is concise but not optimally structured.

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 tool has 4 parameters, no output schema, and no annotations, the description is incomplete. It covers only the hierarchy limitation but fails to explain the return value (e.g., created folder object), parameter semantics, required permissions, or common failure scenarios. An agent would likely need to guess about expected inputs and outcomes.

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?

The input schema has 0% description coverage, meaning no parameter descriptions are provided. The tool description adds minimal parameter insight: it only indirectly relates to 'parentId' by mentioning hierarchy depth. The other parameters (name, order, projectId) receive no explanation of their meaning, constraints, or default values.

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 'Create test case folder' as the primary action, providing a specific verb and resource. It adds context about folder hierarchy limits, but does not explicitly differentiate this create operation from other sibling create tools (e.g., bugs_create, cycles_create). The resource name is clear enough to distinguish it within the test_case_folders group.

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 provides a concrete usage constraint: folder hierarchy is limited to 3 sub-levels, and exceeding that returns a 400 error. This guides the agent on when to avoid using the tool. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., update for existing folders) and does not mention prerequisites like project existence.

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