post_tweet

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

With no annotations provided, the description carries the full safety and side-effect burden. It does disclose meaningful behavioral traits: the tweet will be posted immediately and become publicly visible from the authenticated user's account. However, it does not mention irreversibility, rate limits, or potential posting failures.

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 two short sentences and entirely front-loaded. The first sentence states the core action, while the second adds important side-effect context without any wasted words.

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 one-parameter tool with a clear public side effect and an output schema, the description is mostly complete. It communicates the key facts: who performs the action, what happens, and when visibility occurs. It could be more thorough about limitations or exclusions, but overall it is sufficient.

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 already provides 100% coverage by describing 'text' as 'The tweet content (max 280 characters)'. The description adds no additional parameter-level semantics, but the schema alone is sufficient for a single simple parameter.

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 and resource: 'Post a tweet from the authenticated user's account.' It is specific enough to distinguish this tool from siblings like draft_tweet, reply_to_tweet, and retweet by implying a brand-new, instantly published 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 implies usage for creating and immediately publishing a tweet, and the 'immediately and publicly visible' phrasing gives useful context. However, it does not explicitly state when not to use it or name alternatives such as draft_tweet or reply_to_tweet.

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