delete_test_case

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

With no annotations, the description must disclose behavioral traits, but it only mentions API availability and omits whether deletion is permanent, what data is affected, or required permissions. The caveat is useful but does not cover the core behavioral expectations of a destructive operation.

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?

Two sentences, with the main purpose as a clean first sentence and a critical caveat in the second. No waste, no redundant phrasing, and important warning is front-loaded after the primary action.

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 one-parameter delete tool, the description covers the purpose and a key availability caveat, but with no output schema and no annotations it leaves out typical expectations like return value or confirmation behavior. It is minimally viable but lacks the detail an agent might need to fully trust and post-process the operation.

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 description says 'by internal id', which clarifies that testCaseId is a system-internal identifier, but it does not specify format, examples, or how to obtain the ID. Since schema description coverage is 0%, this modest clarification raises the score from 1 to 3, but the parameter semantics remain thin.

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 the action ('Delete') and the specific resource ('a test case'), with the qualifier 'by internal id' distinguishing it from side-effect-free reads and other delete tools in the sibling list. It unambiguously tells an agent exactly what operation this tool performs.

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 caveat provides a clear usage prerequisite—verify server support via list_available_api_methods before relying on this tool. It does not explicitly state alternatives or exclusions, but for a targeted delete operation the usage context is sufficiently instructive.

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