Delete Git Account

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

The description adds significant behavioral context beyond annotations: it states the action is permanent, cannot be undone, and specifies consequences like breaking CI/CD. It also clarifies the purpose of the 'confirmed' parameter to prevent accidental deletion.

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 concise, with a single paragraph followed by bullet points for args and returns. Every sentence adds value, and the main action is front-loaded.

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?

The description covers the tool's behavior, parameters, consequences, and return type (confirmation message). Given the availability of an output schema, this is complete and sufficient.

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 description explains all three parameters in detail: gitAccountID (the account ID), accountOwner (optional, for org admins), and confirmed (set to true after explicit confirmation). This adds meaning beyond the schema, especially for the 'confirmed' 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 description explicitly states 'Permanently delete a Git account.' It is a specific verb-resource pair, and the tool name and description clearly distinguish it from siblings like 'update_git_account' and 'get_git_account'.

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?

The description explains the destructive nature and warns about breaking CI/CD if it's the only account linked to a project. While it doesn't explicitly list alternatives or when not to use, the context is clear enough for the agent to understand the tool's purpose and impact.

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