Get home timeline

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

With no annotations, the description carries the burden for behavioral disclosure. It mentions the feed is 'chronological' and tied to the 'authenticated account', providing some transparency about ordering and auth. However, it does not disclose pagination behavior, rate limits, or response structure beyond what the schema implies.

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 concise sentences, front-loaded with the core purpose. The second sentence adds valuable usage context without excess. Every word earns its place.

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 2-parameter tool with no output schema, the description gives the essential purpose and context. It lacks explicit mention of what is returned (e.g., list of posts) and does not detail authentication requirements. It is adequate but has gaps for a fully self-contained description.

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% and the description does not explain the 'limit' or 'cursor' parameters. The word 'scroll' hints at pagination but does not directly describe how the parameters work. With simple parameters and no description compensation, this is below minimal.

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 gets the authenticated account's chronological following feed, which is a specific verb+resource combination. It distinguishes from sibling tools like bluesky_get_author_feed by emphasizing 'following feed' and 'home timeline', though it does not explicitly name alternatives.

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 phrase 'This is the main way to scroll Bluesky' provides clear context for when to use it—as the primary feed browsing tool. It does not explicitly exclude alternatives like bluesky_get_author_feed, but the context is clear enough.

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