delete_provider

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

With no annotations present, the description carries the full behavioral burden, yet it discloses nothing beyond the destructive verb. It does not state whether deletion is irreversible, whether it cascades to dependent assistants, or what permissions are required.

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 one-sentence purpose is front-loaded and waste-free, but the 'Args:' and 'Returns: JSON result.' boilerplate adds little, especially since an output schema already exists and makes the Returns line redundant.

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 destructive mutation tool with zero annotations, the definition is too thin: it omits reversibility, permission requirements, and side effects on related entities. The existence of an output schema only excuses the missing return-value explanation, not the missing behavioral 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?

Schema description coverage is 0%, so the description must compensate. It does clarify that the 'name' parameter is a provider id (beyond the schema's bare 'Name' string), but gives no format, example, or lookup guidance.

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 states a specific verb and resource ('Delete a provider configuration'), so the operation is unambiguous. However, it offers no differentiation from siblings such as delete_assistant or delete_memory, which share the same verb pattern.

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 guidance on when to use this tool versus alternatives like update_provider, and no prerequisites or warnings about the consequences of deletion are given. The agent must infer everything from the verb alone.

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