DeleteLocalTestClass

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

No annotations are present, so the description must fully disclose behavioral traits. It mentions managing lock, update, unlock, and optional activation, which provides some transparency. However, it does not state whether the operation is destructive, if it requires specific authorizations, or what happens if the parent class is not transportable.

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, focused sentence that immediately states the primary purpose and then lists key actions. It is compact and front-loaded, though it could be slightly more structured (e.g., bullet points for steps).

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 deletion tool with three parameters and no output schema, the description covers the main process and behavior. It lacks information about return values, error handling, or prerequisites (e.g., transport request requirements), but given the simplicity of the tool, it is reasonably complete.

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 schema covers all three parameters with descriptions, so the description adds minimal additional meaning. It confirms the role of activate_on_delete but does not elaborate on syntax or constraints beyond what the schema already provides.

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 specifies the action (delete), the resource (local test class), and the method (clearing the testclasses include). It also mentions the steps involved (lock, update, unlock, optional activation), effectively distinguishing it from sibling tools like DeleteClass or DeleteLocalDefinitions.

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 implies usage for deleting a local test class but does not explicitly state when to use this tool versus alternatives like DeleteClass or UpdateLocalTestClass. No when-not or alternative suggestions are provided, leaving the agent to infer from the name alone.

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