post_tweet

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

With no annotations supplied, the description carries the full behavioral burden and largely misses it: it does not state that posting is a public, largely irreversible mutation, whether auth or elevated permissions are required, what rate limits apply, or what the response contains. The only behavioral signal is the word "new", which implicitly says this creates rather than updates.

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?

A single short sentence with the action front-loaded and zero filler. It is efficient, though its brevity is also the source of the missing guidance noted elsewhere.

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 but publicly visible, effectively irreversible write operation with no annotations and no output schema, the definition says nothing about side effects, failure modes, or return value. Simplicity of the schema lowers the bar somewhat, but the mutation semantics remain entirely undisclosed.

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?

There is a single parameter and schema description coverage is 100%, with the 280-character limit enforced in the schema itself. The description adds no syntax, formatting, or content guidance beyond the schema, so the baseline of 3 applies.

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?

Names a specific verb and resource ("Post a new tweet") and the target platform (Twitter), so the action is unambiguous. It does not explicitly contrast with the read-oriented sibling search_tweets, but the write verb makes the distinction obvious enough without opening a schema.

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 no when-to-use guidance, no mention of prerequisites such as an authenticated account or authorization, and no pointer to alternatives among the ten sibling tools. An agent must infer everything about invocation context.

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