Agent Twitter Client MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Post a new tweet' implies a write operation but reveals nothing about authentication requirements, rate limits, error conditions, or what happens when posting succeeds/fails. For a mutation tool with zero annotation coverage, this is inadequate.

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 maximally concise at just three words. Every word earns its place - 'Post' specifies the action, 'new' distinguishes from other tweet operations, and 'tweet' identifies the resource. No wasted words or unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't address what happens after posting, what permissions are required, or how to handle errors. The combination of write operation + missing structured data demands more descriptive context than provided.

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 100%, so the schema already fully documents all three parameters. The description adds no additional parameter information beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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 'Post a new tweet' clearly states the verb ('Post') and resource ('tweet'), making the tool's purpose immediately understandable. However, it doesn't distinguish this from sibling tools like 'quote_tweet' or 'send_tweet_with_poll', which also involve posting tweets with different characteristics.

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. There are multiple tweet-posting siblings (quote_tweet, send_tweet_with_poll) with no indication of when this basic tweet tool is preferred over those specialized versions.

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