Agents: Remove an Agent from Account

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the 'permanently deletes' note is largely redundant. The description does add genuinely useful context beyond annotations: the required auth scheme (User API key in an api-access-token header) and the note that IDs/numbers may arrive in Persian or Arabic-Indic digits and are sent through unchanged.

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?

Front-loads the core purpose, then the endpoint, auth, destructive warning, and encoding note in a compact block with no filler sentences. The closing encoding sentence is somewhat boilerplate but is short and potentially relevant to argument formatting.

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 two-required-param destructive mutation with no output schema, the description covers purpose, endpoint, auth, and irreversibility, and the schema documents both parameters. Only the ambiguity against sibling delete/remove tools keeps it short of fully complete.

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 100% — both id and account_id carry their own descriptions ('The ID of the agent to be deleted', 'The numeric ID of the account'). The description adds no further parameter semantics, so the baseline of 3 applies.

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?

States a specific verb and resource ('remove an agent from the account') and adds the HTTP endpoint, making the operation unambiguous. It does not, however, differentiate from siblings like gapify_delete_agent_bot or gapify_remove_inbox_agent / gapify_remove_team_agent, leaving the agent to infer the agent-vs-agent_bot distinction.

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 tool versus the delete/remove siblings, nor any prerequisites or caveats about irreversibility relative to alternatives. The description only states what the tool does, not when to reach for it.

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