Twitter Api45 MCP Server

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

No annotations provided, so description carries full burden. Fails to clarify what 'broadcasting' means (live Spaces, video stream, etc.), what return type to expect (boolean vs object), error conditions, or rate limiting. Minimal behavioral disclosure beyond the basic action.

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?

Single sentence of 9 words with no redundancy. Front-loaded with action and target. Appropriate length for the tool's simplicity.

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 single-parameter boolean check tool, description is minimally adequate but has gaps. No output schema exists, yet description doesn't indicate what gets returned (true/false, object with broadcast details, etc.) or define the broadcasting scope.

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 has 100% description coverage with example value. Description adds no additional parameter context, but baseline is 3 when schema coverage is high. Neither description nor schema explains what 'rest_id' represents (user ID), though the example suggests numeric string format.

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 uses specific verb 'Checks' with resource 'user broadcasting' and temporal scope 'right now'. It distinguishes from siblings like user_info or user_timeline by focusing specifically on live broadcast status, though 'broadcasting' could be more specific (e.g., Spaces vs live video).

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?

No guidance provided on when to use this tool versus alternatives like spaces_info or user_info. No mention of prerequisites or conditions where this check is preferred.

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