Account timeline

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

Annotations already cover the read-only and open-world profile, so the description's added value is the pagination contract — cursor-paged, max 200 per page — and the ordering/filtering defaults. It doesn't mention rate limits or whether the timeline can be truncated, which keeps it below 5, but the paging disclosure is genuinely useful beyond the annotations.

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 dense sentences with no filler: the resource and ordering come first, then the optional scope, then the paging behavior. Every clause maps to a caller decision.

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 10-parameter read tool with no output schema, the description covers scope, ordering, filtering, and paging adequately, and the schema documents the response shape via the format enum. The omission of max_pages (multi-page retrieval in a single call) is the one behavioral element an agent could get wrong from the description alone.

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 80%, so the baseline would be 3, but the description adds meaning the schema lacks: it clarifies that the date range is optional and that replies and retweets are excluded via optional flags — covering the two boolean parameters that carry no schema description at all. It doesn't clarify max_pages (following multiple pages in one call), which is the least obvious parameter.

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 pair — retrieve an account's tweets in time order — plus the scoping options (date range, reply/retweet exclusion). It implicitly separates itself from timeline-searching siblings like ca_search_tweets, but never names them, so the differentiation is inferential rather than explicit.

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 phrase 'An account's tweets' implies the use case (single-account timeline) but gives no explicit when-to-use guidance, no exclusions, and no pointer to ca_search_tweets, ca_get_tweets, or ca_thread for related retrieval tasks. Usage is inferable from the resource named, which is the definition of a 3.

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