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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds two genuinely useful traits beyond them: results are limited to a single page, and only 'public accounts' are returned. It stops short of describing response shape or whether the page size is fixed.

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?

Two short sentences with the scope and page limit front-loaded and the cursor rule second. Nothing is redundant or padded.

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 two-parameter, read-only listing tool with no output schema, the description covers what is returned (public retweeter accounts, one page) and how to paginate. Minor gaps remain—no mention of page size or what the returned account objects contain—but nothing essential to correct invocation is missing.

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%, and the cursor property already documents 'Omit or "" for the first page' as well as referencing next_cursor. The description's cursor advice largely restates the schema, adding only a conversational condition ('if the user asks'), so baseline 3 applies.

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 one page of public accounts that reposted a single tweet.' This clearly distinguishes it from quoting or replying tools by naming the repost relationship, though it never explicitly names a sibling such as get_tweet_quotes to differentiate.

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?

Gives an explicit conditional rule for the cursor ('Pass cursor only if the user asks for another page'), which is real usage guidance. However, it offers no guidance on when to choose this tool over the related quote/reply/thread tools, leaving that selection to inference from the name.

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