get_user_timeline

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

With no annotations, the description should disclose behavioral traits like authentication needs, rate limits, or side effects. It only mentions API endpoints and output format, lacking details on permissions, error conditions, or data mutability.

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 sections for summary, usage, args, and returns. It is somewhat lengthy but front-loaded with key purpose. Could be slightly more concise, but overall effective.

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 the presence of an output schema, the description covers return format in detail (HTML formatting, forwarding, topics, audit status). It explains two modes of operation. Missing error handling, but overall provides sufficient context for an agent.

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 description coverage is 0%, but the description explains each parameter's meaning and behavior (e.g., user_id empty gets current user, q enables search, max_id for pagination). This adds significant value beyond the bare schema.

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 a user's timeline via specific API endpoints, distinguishes between current user and other users based on user_id, and handles search functionality. It differentiates from siblings like get_home_timeline and get_public_timeline.

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?

Provides conditions for when to use different parameter values (empty user_id, q provided). However, it does not explicitly state when to use this tool over sibling tools, though the name and context imply typical usage.

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