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

No annotations are provided, so the description carries the full responsibility for behavioral disclosure. It adds useful context: the cost of 25 tokens and the prerequisite call to list connected accounts, which implies an authentication/authorization requirement. However, it does not explicitly state that deletion is permanent or irreversible, nor does it describe error scenarios such as attempting to delete a post not owned by the target account. The description is adequate but leaves important behavioral traits unstated.

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 three short sentences, each earning its place: the first states the primary action, the second provides the necessary prerequisite and account-targeting logic, and the third gives the token cost. It is front-loaded with the purpose and contains no filler or redundant wording.

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 simple delete operation with a full output schema and comprehensive parameter descriptions, the description covers the essential context: what it does, how to prepare (connected_accounts), how to choose the target account, and the cost. The main gap is the absence of an explicit irreversibility warning, but the verb 'delete' makes that inferable. Overall, it is sufficiently complete for this tool's complexity.

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%, so all three parameters are already described in the schema. The description adds meaning by telling the agent to call x-twitter.connected_accounts first, clarifying where user_id and user_name values come from and how they relate. It also reinforces the 'either user_id or user_name, never both' rule, complementing the schema without duplicating it.

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 starts with a specific verb and resource: 'Delete a post published by a connected X account.' It clearly distinguishes itself from sibling tools like create_post, edit_post, and delete_bookmark by the action and subject. The scope of 'connected X account' adds clarity about the authorization context, making the purpose unambiguous.

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 gives a clear prerequisite: 'Call x-twitter.connected_accounts first.' It then explains how to target an account with user_id or user_name, including the rule 'not both' and the fallback to the default account. This is actionable usage context, though it does not explicitly contrast with alternative delete tools like delete_bookmark or state when not to use the tool, so it stops short of a 5.

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