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

With no annotations, the description fully carries the behavioral disclosure burden. It covers deduplication, newest-first ordering, per-handle counts, the since-cursor semantics, the 2-50 handle range, the missing from:-OR-splitting capability, the cost per call, and the fact that failed or empty calls are free.

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 front-loads the behavioral core in the first phrase and then packs the limitation, cost, and failure policy into a few compact sentences. There is no filler, no restatement of schema fields, and every sentence contributes useful selection or invocation guidance.

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 straightforward tool with three parameters and no output schema, the description supplies all key operational details: batch size, ordering and dedupe behavior, per-handle counts, incremental cursor, pricing, and failure-cost policy. Nothing essential for selecting or invoking the tool 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 coverage is 100%, so the baseline is 3, but the description adds meaningful constraints not present in the schema: the 2-50 handle count and the purpose of the since cursor as an only-what's-new incremental token. This helps an agent construct valid parameter values.

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 clearly identifies the core function: a batch X/Twitter watchlist that fetches combined recent tweets for 2-50 handles, returned newest first and deduped with per-handle counts and a since-cursor. It lacks a crisp verb phrase like 'fetch' or 'list', and the 'No from:-OR-splitting' note only weakly differentiates it from sibling tools like x_search.

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?

It establishes a clear use case—multiple handles in one call for watchlist-style monitoring—and gives one explicit exclusion: it does not support from:-OR splitting. It also tells the agent how to get credits via buy_credits or /buy/credits, but it does not name sibling alternatives for single-handle or search scenarios.

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