delete_tweet

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

With no annotations provided, the description carries full burden for disclosing behavioral traits. It only states that the tool deletes a tweet, without mentioning irreversibility, permissions needed, rate limits, or side effects. This is minimal disclosure for a destructive action.

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 extremely concise, comprising two clear sentences. The first sentence states the purpose directly, and the 'Args' section efficiently documents the parameter. No unnecessary words are present.

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?

Given the simple one-parameter tool, the description is adequate but not fully complete. It omits important context such as ownership prerequisites (only the tweet author can delete), permanence of deletion, or potential failure conditions. An output schema exists but is not described.

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 schema description coverage is 0%, but the description adds 'tweet_id: The tweet ID to delete.' This clarifies the parameter's purpose beyond the schema's type and title, effectively compensating for the lack of schema documentation.

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 'Delete a tweet by ID', specifying the verb and resource. While the tool name inherently indicates deletion, the description adds the 'by ID' clarification. Among siblings like delete_retweet and delete_scheduled_tweet, it effectively distinguishes this tool for deleting a specific tweet.

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 such as delete_retweet or delete_scheduled_tweet. It does not mention ownership prerequisites, when not to use it, or any context about preferred scenarios.

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