delete_classification

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

Without annotations, the description bears full responsibility for disclosing behavioral traits. It only states 'Delete' which implies destruction, but fails to explain what happens to associated tags, children, or whether the operation is reversible. No mention of required permissions or side effects.

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?

While the single sentence is short, it is underspecified. Conciseness should not come at the cost of missing critical information. The description fails to earn its place by omitting necessary details about parameters and behavior.

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 the absence of annotations and output schema, the description is incomplete. It does not describe the return value, error conditions, or nuanced behavior. For a mutation tool with three parameters, more information is needed for correct usage.

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?

Schema description coverage is 0%, so the description must add meaning to parameters. It does not. The parameter names (classification_id, hard_delete, recursive) are present in the schema but the description offers no explanation of their semantics, such as what 'hard_delete' or 'recursive' entail.

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 resource 'classification' from OpenMetadata. It is specific enough to distinguish from other delete tools targeting different entities, though it lacks extra detail to differentiate it from update_classification.

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 provides no information on when to use this tool versus alternatives like update_classification or other delete tools. No prerequisites, consequences, or exclusions are mentioned, leaving the agent without guidance on appropriate usage.

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