get_v1_user_search_followers

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 only states it's a GET request that searches, but lacks details on behavioral traits like pagination, rate limits, or any side effects. The 'force' parameter's description is in the schema, not the tool description.

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 very short but wastes space reiterating the HTTP method and path in brackets, which is already implied by the tool name. The remaining content is minimal and does not provide sufficient information for an agent.

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?

With no output schema, low schema coverage, and no annotations, the description is severely incomplete. It does not explain what the tool returns, how to interpret results, or how it differs from numerous sibling tools, leaving the agent without critical context for correct usage.

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 only 33% (only 'force' has a description). The tool description adds no explanation for 'user_id' or 'query', leaving the agent to guess their meaning. Given the low coverage, the description should compensate but fails to do so.

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 states 'Search users by followers' which indicates a search operation but is ambiguous: it could mean searching for users that are followers of a given user or searching for users based on their followers. The title 'Search Followers' leans toward the former, but the distinction from sibling 'get_v1_user_search_following' is unclear.

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 on when to use this tool versus alternatives. There are many sibling tools with similar names (e.g., get_v1_user_search_following, get_v1_user_followers_chunk), and the description does not provide any conditions or exclusions.

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