get_user_info_batch

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

No annotations provided, so description carries full burden. It fails to disclose important behaviors like maximum batch size, error handling for invalid usernames/user_ids, or data freshness of profiles. Minimal behavioral context.

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, no redundancy, directly conveys core function. Front-loaded with key information.

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 batch nature and lack of output schema, description omits critical details like return format, ordering, and per-element error handling. Insufficient for an agent to confidently use without risking surprises.

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 covers all 2 parameters with descriptions. Description adds that you can provide 'usernames and/or user_ids,' which clarifies optionality but adds little beyond schema. Baseline 3 for high coverage.

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 'get public profiles for multiple X/Twitter accounts in one request,' specifying verb (get), resource (public profiles), and scope (multiple, batch). Distinguishes from sibling get_user_info which is for a single account.

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?

Implies use for batch requests but does not explicitly contrast with single-user alternatives or provide criteria for when to choose this tool over others, such as get_user_info or other user-related tools.

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