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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), and the description meaningfully adds beyond them: it discloses pagination mechanics (has_next_page + next_cursor) and an explicit credit cost model (15 per user, min 15, waived on bulk). These are genuinely useful operational traits an agent cannot get from annotations. It stops short of auth or rate-limit details.

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 lines, front-loaded with the core purpose, then pagination, then cost. Every clause carries distinct information with no repetition. The structure is easy for an agent to parse at a glance.

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 explains the pagination envelope (has_next_page + next_cursor) and the cost, which covers most of what an agent needs. The shape of the returned account objects themselves is not described, which is the only real gap for a simple two-parameter read tool.

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 coverage is 0%, so the description must carry the parameter burden. It does explain the cursor parameter well by tying next_cursor to cursor for continuation, but tweetId is only implied by "a post" and gets no format or type clarity. Partial compensation, so a 3.

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 states a specific verb and resource ("List the accounts that reposted a post") with the scope tightly bound to a single post. It naturally distinguishes this from siblings like tweet_quotes and tweet_replies, which target different relationships to the same post. An agent can identify the correct tool without opening the schema.

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?

Usage is implied by the purpose, and the pagination note explains how to continue a result set, but there is no explicit when-to-use/when-not guidance or named alternatives. Relevant siblings such as tweet_quotes or tweet_replies (other ways to enumerate accounts around a post) are never referenced. Minimum-viable rather than instructive.

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