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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention that this is a read-only lookup, whether authentication is required, how pagination works, or the meaning of billing credits. The phrase 'Billing per call: 1 Credits' is the only behavioral hint, but it's not informative for selecting or using the tool correctly.

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 extremely short, but it under-specifies rather than being concise. 'Retweeters by V2 Group: Tweets. Billing per call: 1 Credits.' is only 11 words, not enough to convey purpose even though it is front-loaded. The billing note is marginal and doesn't compensate for the lack of meaning.

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 tool complexity (5 parameters, no output schema, no annotations, and many sibling tools), the description is completely inadequate. There is no mention of what the tool returns, how to format parameters, what tweetId should be, or how the cursor is used for pagination. The agent has essentially nothing to rely on beyond the parameter names.

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 20%, with only auth_token having a description. The tool has 5 parameters including cursor, tweetId, proxyUrl, and resFormat, none of which are explained in the description or schema. The description adds no parameter-related meaning beyond what's in the schema, so the agent cannot confidently construct a request.

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 says 'Retweeters by V2 Group: Tweets' which is a label-like phrase that restates the tool name without a clear verb or action. It only vaguely indicates that the tool relates to retweeters via V2 API and the 'Tweets' group, but does not state what it actually does (e.g., 'get retweeters of a tweet'). It is too terse to distinguish from sibling tools like retweetersIds or favoritersV2.

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?

There is no guidance on when to use this tool versus alternatives. The description provides no context, no exclusions, and no mention of alternatives like retweetersIds or favoritersV2. It only lists the tweetId parameter implicitly through the schema but gives no usage scenario.

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