twitter_home_timeline

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds value by detailing the return format ('tweets with author and metrics plus a cursor') and authentication requirements ('Requires an authenticated session behind your key'). It does not contradict annotations and provides useful behavioral context.

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 concise—four sentences front-loaded with the primary purpose. Every sentence provides essential information without redundancy. It efficiently covers purpose, usage, return data, and high-level guidance.

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 tool has 6 parameters (none required) and no output schema, the description adequately covers pagination, authentication, and general return data. It could mention rate limits or typical response size, but the current completeness is sufficient for an agent to invoke the tool correctly.

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 100%, so baseline is 3. The description enriches parameters with practical details, such as the typical range for 'count', pagination instructions for 'cursor', and usage notes for 'proxy_url' (recommended for writes). This adds significant value beyond the schema descriptions.

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 the tool retrieves the authenticated user's home timeline, specifying 'Get YOUR authenticated account's Home timeline (the 'Following'/'For you' feed), most recent first.' This verb+resource combination is specific and distinguishes it from sibling tools like twitter_advanced_search or twitter_user_tweets.

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 explains when to use the tool ('to read what your account would see when it opens X') and notes the requirement for an authenticated session. It implies a read-only context but does not explicitly exclude alternative tools for similar purposes, such as twitter_advanced_search. The guidance is clear but lacks explicit when-not-to-use statements.

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