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

With annotations already declaring readOnlyHint=true and openWorldHint=true, the description adds useful behavioral context: it explains pagination return fields ('has_next_page + next_cursor'), how to continue paging, and the credit cost model. It does not cover authentication or rate limiting beyond credits, but for a read-only paginated endpoint this is a strong disclosure.

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 three short, front-loaded lines: purpose first, then pagination mechanics, then credit cost. Every sentence carries actionable information, and there is no filler.

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 simple, read-only, paginated endpoint with annotations covering safety and open-world behavior, the description explains the return pagination model and credit cost. It omits tweetId semantics, but an agent can infer that tweetId identifies the tweet whose quotes are paginated; the remaining omission is minor rather than blocking.

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 0%, so the description must compensate. It partially does by explaining that 'next_cursor' should be passed as 'cursor' for more results, which adds real meaning beyond the schema. However, it says nothing about the required 'tweetId' parameter — its format, source, or behavior — leaving a significant gap for one of only two parameters.

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 gives a specific verb and resource: 'Page through quote posts,' and adds a parenthetical definition — 'reposts that added commentary' — that distinguishes quote posts from retweets and replies. It does not explicitly name sibling alternatives, but the resource itself is clear enough for an agent to distinguish it from tools like tweet_replies or tweet_retweeters.

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?

The description implies the use case by defining quote posts as reposts with commentary, which helps distinguish this tool from reply- and retweet-focused siblings. However, it never states when to choose this over alternatives or any exclusions, so guidance is only implied rather than explicit.

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