Agent Twitter Client MCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Follow a Twitter user,' which implies a mutation/write operation, but doesn't describe any behavioral traits such as authentication requirements, rate limits, error conditions (e.g., invalid username), or what happens on success (e.g., confirmation message). This leaves significant gaps for safe and effective use.

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, direct sentence: 'Follow a Twitter user.' It is front-loaded with the core action and resource, with zero wasted words. Every part of the sentence earns its place by conveying essential purpose without redundancy.

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 complexity (a mutation tool with no annotations and no output schema), the description is incomplete. It doesn't address behavioral aspects like authentication needs, rate limits, or response format, which are crucial for a write operation. While the schema covers the single parameter well, the overall context for safe and informed use is lacking.

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 has 100% description coverage, with the 'username' parameter clearly documented as 'Username to follow (without @).' The description doesn't add any parameter details beyond what the schema provides, but since schema coverage is high, the baseline is 3. It gets a 4 because with only one parameter, the description's lack of additional info is less critical, and the schema fully compensates.

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 ('Follow') and resource ('a Twitter user'), making the purpose immediately understandable. It distinguishes from siblings like 'get_followers' or 'get_following' by being a write operation rather than a read operation. However, it doesn't explicitly differentiate from other social actions like 'like_tweet' or 'retweet' beyond the verb itself.

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. It doesn't mention prerequisites (e.g., authentication status), when not to use it (e.g., if already following), or compare it to similar tools like 'get_following' for checking follow status. The agent must infer usage from the tool name alone.

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