groups_ai_providers_delete_ai_provider

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Delete provider' signals a mutation, but it says nothing about irreversibility, required permissions, whether dependent settings are cascaded, or what is returned. For a destructive operation this is a real gap.

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 first three segments are reasonably front-loaded, but the bulk of the text is keyword spam ('remove provider, destroy provider, write provider, ... mealie'), which adds no selection value and bloats the definition.

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 single-parameter destructive tool with no annotations and no output schema, the description should at minimum warn about irreversibility and prerequisites. It supplies none of that, leaving the agent to infer the entire risk profile from the word 'Delete'.

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% and the description adds no meaning for provider_id beyond the 'DELETE /api/groups/ai-providers/providers/{provider_id}' template, which at least shows it is a path parameter. It never explains how to obtain a valid provider_id or what happens if one is wrong.

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 pairs a clear verb ('Delete') with the resource ('Ai Provider') and scopes it to the 'Groups: AI Providers' collection, so an agent can distinguish it from groups_ai_providers_create_ai_provider, _get_, and _update_. It stops short of stating consequences, but the core purpose is unambiguous.

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?

There is no guidance on when to use this versus the sibling CRUD operations, nor any precondition (e.g., that the provider must exist, or that this is the destructive counterpart to update). The endpoint template implies a REST delete but doesn't tell the agent when invoking it is appropriate.

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