get_user_followers

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

Discloses ordering (reverse chronological), metadata included, pagination via cursor, and limitation for large accounts. No annotations exist, so description carries full burden. Lacks specifics on rate limits, authentication, or error handling, but covers core behavior well.

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?

Concise 4-sentence description. Front-loaded with primary action, then ordering and metadata, then pagination and usage note. Every sentence adds value; no 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?

Covers purpose, ordering, metadata, pagination, and large account handling. Lacks output schema details and error scenarios, but for a simple list tool with well-documented parameters, it is reasonably complete.

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 coverage is 100%, so baseline is 3. Description adds minor value (userName without @, cursor from previous response). Otherwise reinforces schema. No significant additional semantic depth.

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 'Fetch followers of a Twitter/X user' with specific verb and resource. Distinguishes from siblings like get_user_followings, get_user_info. Provides usage context (analyze followers, build audiences, competitive analysis).

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?

Explicitly mentions pagination for large accounts and that one call won't return all followers. Implies when to use (analyze followers) but lacks explicit when-not-to-use or comparison with sibling tools.

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