test_case_folders_delete

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

Discloses critical behavioral details: hard-delete of test cases, cascade removal of child folders, and alignment with front-end. Missing info on reversibility or side effects, but adequate for a delete tool.

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?

Three concise sentences convey purpose, scope, and key behavior without redundancy. Efficiently 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?

For a single-param delete operation with no output schema, the description fully covers destructive actions and front-end equivalence, leaving no ambiguity.

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?

Single 'id' parameter with schema description 'Test Case Folder ID' provides necessary meaning; description adds no extra clarification, but 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?

Description clearly states 'Delete test case folder' and elaborates on the destructive scope (hard-deletes contained test cases and child folders), distinguishing it from sibling CRUD operations.

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?

No explicit when-to-use or when-not-to-use guidance beyond the obvious delete purpose. However, the behavior description clarifies it's a hard delete, implying careful use.

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