post_tweet

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

No annotations are provided, so the description carries the full burden. It states 'Post a tweet' which implies a write/mutation operation, but doesn't disclose behavioral traits like authentication needs, rate limits, whether it's idempotent, or what happens on failure (e.g., duplicate tweets). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the core action ('Post a tweet') and lists optional features without waste. Every word earns its place, making it easy to scan and understand quickly.

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's complexity (mutation with 4 parameters), no annotations, and an output schema (which reduces need to describe returns), the description is minimally adequate. It covers the basic purpose and parameters but lacks behavioral context and usage guidelines, making it incomplete for safe, effective use by an agent.

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 mentions 'optional media, reply, and tags' which maps to three parameters (media_paths, reply_to, tags) and implies text is required, adding some meaning beyond the bare schema. However, it doesn't explain parameter formats (e.g., what media_paths expects, how tags differ from text) or constraints, leaving gaps.

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 action ('Post a tweet') and mentions optional features (media, reply, tags), which distinguishes it from read-only sibling tools like get_timeline or get_tweet_details. However, it doesn't explicitly differentiate from other tweet-creation tools like create_poll_tweet, which is a minor gap.

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 like create_poll_tweet for polls or reply_to for threading context. It mentions optional features but doesn't specify prerequisites, constraints, or typical use cases, leaving the agent to infer usage from parameter names alone.

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