Everything in a window

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral constraints: the 31-day maximum window and cursor-paged retrieval. It does not disclose rate limits, return format behavior, or what happens when max_pages is reached.

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?

One dense sentence with the key scope and constraint front-loaded. Every phrase adds information: the resource, the window boundary, the maximum window size, account scope, and pagination behavior.

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?

The description covers the essential retrieval shape and window constraint, which is enough to understand the tool's purpose. However, for a six-parameter paginated query tool with no output schema, missing date format details and limit/max_pages semantics leave meaningful gaps for correct invocation.

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?

With only 50% schema description coverage, the description must compensate but only partially does so. It explains the since/until window and the 31-day cap, but omits the date format for since/until, the meaning of limit, and how max_pages interacts with cursor paging.

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 states that it retrieves archived tweets within a date window across all accounts. This distinguishes it from account-scoped siblings like ca_account_tweets and search-oriented siblings like ca_search_tweets, though it does not name alternatives explicitly.

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 'across all accounts' and the date window, suggesting broad bulk retrieval rather than targeted search or single-account queries. However, there is no explicit guidance on when to prefer this over ca_search_tweets, ca_get_tweets, or ca_account_tweets.

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