delete_scheduled_tweet

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

No annotations are provided, so the description carries the burden. It mentions rate limits ('follow X's standard rate limits, no special caveats needed'), which is useful. It does not disclose deletion irreversibility or other side effects, but for a simple delete operation this is acceptable.

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 three short sentences plus an arguments section. It is front-loaded with the core purpose, then adds rate limit context and parameter details. No extraneous content.

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 tool has only one parameter and an output schema (not shown but present), the description covers the essential identifier clarification and rate limit behavior. It is complete enough for a straightforward delete operation.

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 0%, so the description must compensate. It adds meaning to scheduled_tweet_id by explaining its origin (from create_scheduled_tweet or get_scheduled_tweets) and emphasizing it is NOT a regular tweet ID, which is critical for correct usage.

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 verb 'Delete' and the resource 'scheduled tweet', specifying the identifier 'scheduled tweet ID'. It distinguishes from siblings like delete_tweet and delete_bookmark by focusing on scheduled tweets.

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 clarifies the source of the ID (create_scheduled_tweet or get_scheduled_tweets) and explicitly states it is not a regular tweet ID, guiding correct parameter usage. However, it does not compare to alternatives like delete_tweet for posted tweets.

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