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

With no annotations, the description carries the full behavioral disclosure burden. It does disclose the search-by-keyword behavior and what profile fields are returned, which is useful, but it omits details such as result limits, pagination effects, authentication requirements, or how missing/blocked profiles are handled.

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?

Two concise sentences with no filler. The main action is front-loaded, and the return-value highlights are clearly stated, making it easy for an agent to parse.

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 low complexity of the tool, this is serviceable but not fully complete. There is no output schema, so the description should clarify whether the result is a list of profiles and how the pages parameter affects the returned data; it only says 'Returns profile data'.

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 covers both parameters fully (query required, pages with default and range), so the baseline is 3. The description adds no additional parameter nuance beyond confirming that the keyword is used for searching.

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 identifies the action ('Search Twitter/X users by keyword'), the resource (users), and the main output fields (username, bio, follower counts, verification status). It is specific enough to understand the tool's role, though it does not explicitly contrast with sibling tools such as search_twitter or twitter_user_profile.

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 is provided on when to use this tool versus alternatives like search_twitter, twitter_user_profile, or twitter_user_followers. The description explains what it does but not the conditions that would make it the right choice.

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