DeleteCdsUnitTest

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

The description discloses the destructive nature via the verb 'delete', but provides no additional behavioral context. With no annotations, the agent receives no information about reversibility, required authorizations, error handling, or side effects, which is critical for a deletion 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?

The description is a single, front-loaded sentence that efficiently states the tool's purpose. It is appropriately short but could incorporate more detail without sacrificing conciseness, such as a brief note on transport requirements.

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 no annotations, the description fails to provide complete context for a delete operation. It does not mention what the tool returns, required permissions, or behavior when the class does not exist, leaving gaps for the agent.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds no further meaning to the parameters beyond what the schema already provides; for example, it does not elaborate on the transport_request role or format.

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 (CDS unit test class, global class). It distinguishes from sibling tools like DeleteUnitTest and aligns with CreateCdsUnitTest and UpdateCdsUnitTest, leaving no ambiguity about the tool's function.

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 guidance is provided on when to use this tool versus alternatives or what prerequisites exist. The transport_request parameter is required for transportable packages, but the description does not explain this context or when it is needed. No exclusions or comparisons with DeleteUnitTest are mentioned.

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