Delete Generation Model

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

The description goes beyond the annotation's destructiveHint by detailing specific behavioral traits: it 'cascades to associated test runs and test data points' and is irreversible ('This cannot be undone'). This adds meaningful context about the destructive scope that the annotation alone does not convey.

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 concise and front-loaded with the action. It includes two brief sentences and an Args list, all of which add value. It could be slightly tighter by merging the first two sentences, but there is no waste and the structure is clear.

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 simple delete tool with one required parameter, the description is nearly complete. It covers the action, cascading effects, irreversibility, and the parameter meaning. The presence of an output schema and annotations reduces the need to describe return values or safety flags, making this sufficiently comprehensive.

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 only provides the parameter name 'Name' with no description. The description's Args section supplies semantic meaning: 'Name of the registered generation model to delete.' This clarifies exactly what value is expected, fully compensating for the 0% schema description coverage.

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 identifies the tool's purpose: 'Remove a registered generation model and all its related test data.' It uses a specific verb ('remove') and resource ('generation model'), and explicitly mentions the cascading scope. This distinguishes it from sibling tools like update_generation_model or get_generation_model.

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 the use case (deleting a model) and includes a strong caution ('This cannot be undone'), but it does not explicitly state when to use this versus alternatives, nor does it mention any prerequisites like listing models first. There are no exclusions or when-not-to-use guidance, so it is adequate but not highly instructive.

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