delete_datasource_type

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

With no annotations, the description must disclose behavioral traits. It only says 'Delete a datasource type,' which implies destructive behavior but does not explain consequences (e.g., permanence, cascading deletes, permission requirements). This is a significant gap for a delete operation.

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, short sentence that is easy to parse. It is sufficiently concise, but the brevity comes at the cost of omitting critical safety context, earning a 4 rather than 5.

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 simple signature (one parameter) and no output schema, the description is structurally minimal. However, the lack of behavioral disclosure and usage guidance means the tool is not adequately contextualized for an agent, leaving it incomplete for a destructive operation.

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 already fully documents the single parameter type_id as 'Type ID' (100% coverage). The description does not add additional parameter context, so the baseline of 3 applies; no enhancement or deficit is present.

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 'Delete a datasource type' clearly states the action (delete) and the resource (datasource type), distinguishing it from sibling tools like delete_datasource_type_folder or delete_script_folder. The purpose is unambiguous and directly conveys 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 usage guidance is provided. The description does not mention when to use this tool, any prerequisites, or alternative tools (e.g., search_datasource_types before deletion). It only states the operation, leaving the agent without context for when to invoke it.

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