github_enterprise_teams_delete

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

No annotations, so description carries full burden. It does not disclose that deletion is destructive and irreversible, nor does it mention authorization requirements, side effects, or what happens to associated resources. The description is too minimal 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, which is concise and front-loaded. However, it is overly minimal, sacrificing necessary detail for brevity.

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 delete operation with two required parameters and no output schema, the description lacks behavioral context, parameter semantics, and usage conditions. It is incomplete for an AI agent to safely and correctly invoke the tool.

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 input schema has 100% description coverage, but descriptions are just the parameter names ('enterprise', 'team_slug'), adding no meaningful semantics. The general description does not elaborate on parameters, leaving them under-documented.

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 an enterprise team' clearly states the verb (delete) and resource (enterprise team), which is specific. It distinguishes from siblings like create, get, list, and update, but does not explicitly differentiate from other delete operations (none present in siblings).

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, no prerequisites (e.g., team existence, permissions), and no when-not-to-use conditions. The description provides no usage context.

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