Remove Facebook Account

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

Annotations already declare destructiveHint=true, so the agent knows this is destructive. The description adds clarity that the destruction is limited to the cookie set, which is useful. However, it does not disclose side effects like whether the account is also removed from the account list or if this affects the active session, leaving some behavioral gaps.

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 sentence that is front-loaded with the verb 'Remove' and a clear object. It contains no filler or redundant information, making it highly concise and well-structured.

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 single-parameter destructive tool with an output schema present, the description is mostly complete. It explains the core action and scope. However, it could mention whether the removal is permanent or if the account must exist, but these are minor omissions given the simplicity and the available schema.

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 fully documents the only parameter, account_id, with a description 'The account id to remove'. The tool description adds no additional parameter-level detail, so it relies entirely on the schema. With 100% schema coverage, a baseline of 3 is appropriate.

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 clearly states the action: remove, and the target: a stored Facebook identity's cookie set. This is specific and distinguishes it from siblings like update_account_cookies or close_session. Although the title says 'Remove Facebook Account', the description scopes it precisely to the cookie set, avoiding ambiguity about deleting the actual 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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, such as the account needing to be stored, or scenarios like removing an inactive account vs switching away. The agent must infer usage from the tool name and sibling context, which is not explicit.

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