delete_team

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

With no annotations, the description carries the full behavioral burden and does supply one useful fact: the `teams:manage` permission requirement. However, it says nothing about irreversibility, what happens to team members or assigned conversations on deletion, or whether a confirmation step exists — critical context for a destructive 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 definition is front-loaded and minimal: action, permission, endpoint, tag. Nothing is redundant or buried, and every line is scannable for an agent selecting a tool.

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 one-parameter destructive tool with no output schema, the description covers identity and auth but omits the side effects an agent most needs — cascading removals, member unassignment, and irreversibility. It is callable as written but incomplete for safe invocation.

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?

Only one parameter exists and schema coverage is 100%, so the schema already documents `id` as a path parameter. The endpoint text reinforces that the id identifies the team being deleted, adding modest confirmation without contradicting the schema; baseline 4 applies for a single well-documented parameter.

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 definition opens with a specific verb+resource ('Delete Team') and reinforces it with the endpoint 'DELETE /api/v1/teams/{id}', leaving no ambiguity about the operation. It does not explicitly contrast with siblings such as update_team, but the name and endpoint make the destructive scope unmistakable.

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 when-to-use guidance, no statement of prerequisites beyond the permission name, and no alternatives offered (e.g., update_team or remove_team_assignee for softer changes). An agent must infer entirely from the tool name when this is appropriate versus other team operations.

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