get_user_info

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

No annotations are provided, so the description carries full burden. It implies a read operation but does not explicitly confirm idempotency, required permissions, rate limits, or potential side effects. Basic purpose is clear, but behavioral constraints are absent.

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 is efficient and front-loaded. Every word earns its place. Could be slightly improved by adding structure (e.g., listing what profile fields are returned), but not verbose or wasteful.

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 tool with one parameter and no output schema, the description is adequate but not comprehensive. It fails to specify what 'profile information' includes (bio, follower count, etc.) or error handling. While simple, an agent might need more detail to parse results effectively.

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 100%, and the parameter description in the schema already clarifies 'usernames (without @ prefix)'. The tool description adds no extra meaning beyond that. Baseline 3 is appropriate as no further enrichment is needed.

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?

Description clearly states the verb 'Get' and resource 'profile information for one or more X/Twitter users by username'. This distinguishes it well from sibling tools which are all tweet-related (post, search, timeline, like, retweet, delete). No ambiguity.

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 (e.g., search_tweets for user lookup by other criteria). No mention of prerequisites, rate limits, or authentication requirements. The description simply states what it does, not when or how to decide.

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