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

Annotations already declare readOnly, non-destructive, openWorld, so the safety profile is covered. The description adds genuinely useful context beyond them: pagination-based billing ('$0.006 per page') and the shape of the return ('profile details for each user'). It does not describe pagination limits or rate-limit behavior, keeping it from a 5.

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?

Three short sentences with zero waste, front-loading the core purpose before the alternative and the cost note. Every sentence carries distinct 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?

With no output schema, the description helpfully signals the return content ('profile details for each user') and the cost model. It leaves minor gaps on pagination ceilings and return ordering, but is adequate for a straightforward read tool whose annotations cover safety.

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%, so both parameters are already documented in structured form; baseline 3 applies. The description reinforces that tweet_id is numeric but adds no syntax or default detail for 'pages' beyond what the schema states.

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?

States a specific verb and resource ('Get the users who retweeted a tweet') plus the keying method ('by numeric tweet ID'). It explicitly names the sibling it is not (twitter_tweet_quotes) and the distinguishing condition, so an agent can separate it from adjacent tools without opening schemas.

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?

Explicitly routes the ambiguous case to twitter_tweet_quotes ('retweets that added a comment'), which is the main source of confusion for this tool family. It stops short of covering broader when-to-use context or other alternatives like twitter_tweet_details, so it is clear but not exhaustive.

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