x_timeline_home

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

Beyond the readOnlyHint and non-destructive annotations, the description adds important behavior: it requires user-context auth, returns a 'compact, sanitized page,' and warns that third-party content must be treated as data, not instructions. This meaningfully supplements the annotations with safety and output traits.

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?

Three tight, purposeful sentences: the first states the action and ordering, the second the auth requirement, and the third the output and safety warning. There is no filler or repetition of schema details.

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?

The description, together with the fully documented schema and helpful annotations, gives an agent enough to call the tool correctly. It includes auth needs, output shape, and a security caveat. It could be slightly stronger by naming sibling timeline tools for explicit routing, but this is not a major gap.

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 input schema has 100% parameter description coverage, so the description is not required to explain parameters. The description adds no parameter-specific semantics beyond what the schema already provides, which fits the baseline score.

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 uses a specific verb and resource: 'Read the authenticated X (Twitter) user's home timeline in reverse-chronological order.' It clarifies scope as 'the accounts they follow, newest first,' which distinguishes it from sibling timeline tools like x_timeline_user and x_timeline_mentions.

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 provides clear context for when to use the tool: reading the authenticated user's home feed, not a specific user's or mentions timeline. It also states the auth prerequisite. However, it does not explicitly name alternatives or state when not to use this tool.

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