get_timeline

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

Annotations are absent, so the description carries the burden. It states that it returns tweets with text, author, engagement metrics, and URLs, which gives some behavioral insight. However, it does not disclose any pagination behavior, authentication requirements, or rate limits, which would be common for a read operation that might have pagination.

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 two sentences, front-loaded with the main action, and includes a return-value summary. Every sentence adds value, and there is no redundancy.

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 simple read operation with a single fully described parameter and an output schema, the description is nearly complete. It could mention pagination or the nature of the timeline, but given the simplicity and the presence of an output schema, it is sufficient.

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?

The schema has one parameter (max_results) with 100% description coverage, so the schema already explains it. The description does not add much beyond that, but the baseline of 3 is elevated to 4 because the schema is fully covered and the default is described, making the description unnecessary for parameters.

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 retrieves recent tweets from the user's home timeline, which is specific and distinct from siblings like get_mentions or search_tweets. However, it does not explicitly contrast with siblings, but the resource and scope are clear.

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 says 'Use this to see what's happening in the user's feed,' which implies usage context, but it does not mention when not to use it or suggest alternatives (e.g., for mentions or specific tweets). This is adequate but lacks exclusions.

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