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

Without annotations, the description must disclose behavioral traits. It states that results are billed per item and that resultsLimit is mandatory, implying a cost-aware read operation. It does not mention idempotency, rate limits, or authentication requirements. Since it is a read tool, no destructive behavior is expected, but more context would improve transparency.

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 well-structured with two paragraphs: the first states the main purpose and scope, the second provides usage guidance. Sentences are concise and avoid redundancy. It is slightly long but every sentence adds value, and the critical information is front-loaded.

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?

Given 9 parameters and no output schema, the description covers the core usage: timeline types, mandatory resultsLimit, and optional filters. It explains what is returned (tweets, lists, engagement data) but does not detail the response format or pagination. For a complex tool, this is mostly complete.

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 33%, so the description adds significant value. It lists all 'kind' enum values, explains their mapping to user/tweet IDs, and describes optional filters as 'search-operator filters.' The 'resultsLimit' parameter is reemphasized as mandatory and billed. This goes beyond the schema, though some parameters (e.g., 'language') are not detailed individually.

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 it fetches a user's X/Twitter timeline and enumerates specific sub-timelines (tweets, replies, likes, media, mentions), follower/following lists, and engagement lists. The verb 'fetch' and resource 'timeline' are specific, and the scope is well-defined, distinguishing it from sibling tools that likely handle other X operations.

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 provides explicit guidance on how to use the 'kind' parameter with all enum values and emphasizes that 'resultsLimit' is mandatory and billed per item. It also mentions search-operator filters. However, it does not explicitly state when to use this tool vs. alternatives (e.g., x_search) or when not to use it, which slightly reduces clarity.

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