post_tweet

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

Implies a write operation but lacks details on consequences (e.g., immediate visibility, deletion possibility, rate limits). No annotations provided, so description carries full burden yet remains minimal.

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?

Two short sentences that are direct and front-loaded; every word adds value.

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?

Adequately covers purpose and basic usage for a simple post tool with two parameters and no output schema. Lacks error/result details but sufficient for straightforward action.

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 covers both parameters (text and reply_to_tweet_id) with descriptions. The description only repeats the 280-char limit already in schema, adding no new meaning.

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?

Clearly states 'Post a tweet from @agentbtcio' and lists use cases (launches, updates, discussions). Distinct from sibling tools like search_x or get_mentions.

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?

Provides explicit contexts for use (announcing launches, updates, responding) but does not mention when not to use or suggest alternatives like reply vs. new tweet.

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