delete_classifier

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

While the destructiveHint annotation already indicates destructive behavior, the description adds important behavioral details: the tool cannot delete ALTR managed classifiers, and it is restricted to user-created classifiers. This provides context beyond the annotation.

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 highly concise, consisting of two short sentences. It front-loads the primary purpose and immediately follows with usage restrictions, with no wasted words.

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?

The tool is simple (one parameter, destructive), and the description covers purpose and usage restrictions. An output schema exists, so return values are not needed in the description. The description adequately addresses the tool's scope without missing critical context.

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 already fully describes the single parameter (classifier_name) with a clear description. The tool description adds no additional parameter semantics, so the baseline score of 3 applies given the high schema 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 states the tool removes a custom classifier, using the verb 'Remove' and specifying the resource 'custom classifier you created'. It distinguishes itself from other delete tools by clarifying it only applies to user-created classifiers, not ALTR managed ones.

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 explicitly states when to use the tool ('Only use for classifiers you created with `create_classifier`') and when not to use it ('Cannot delete ALTR managed classifiers'), providing clear guidance on appropriate contexts.

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