BearQ: Delete Test Cases

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

Annotations already mark the operation as destructive and non-read-only, but the description adds meaningful nuance: deletion is reversible, test cases are archived and restorable, and protected tests are rejected. This goes well beyond what annotations provide.

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 compact and front-loaded: first the action, then the reversibility nuance, then the constraint. Every sentence carries useful information with no filler or redundancy.

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-parameter tool with rich annotations and full schema coverage, the description provides everything needed to invoke it correctly. No output schema exists, but return details are not essential for a delete operation with clearly stated behavior.

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 covers 100% of parameters and fully describes testCaseIds. The description only paraphrases the schema by saying deletion is by ID, so it adds no meaningful new parameter-level meaning. Baseline 3 applies.

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 ('Deletes'), a specific resource ('BearQ test cases'), and a specific selection method ('by ID'). It also clarifies the behavior for protected versus unprotected tests, making the tool's purpose unambiguous and distinct from sibling run/expand tools.

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?

Clearly indicates that this tool works on unprotected tests and that protected tests are rejected, which gives an explicit when-to-use condition. It does not name an alternative tool, but none of the siblings appear to offer the same delete operation, so this is sufficient context.

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