Read your home timeline

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds useful behavioral context: the feed is ordered newest-first and requires a connected account, but it does not disclose output shape or pagination behavior beyond what the parameter schema already states.

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?

Two short sentences carry all the essential context: what the feed contains, its ordering, the alternative parameter mode, and the account requirement. There is no filler or repetition.

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 rich parameter schema and read-only annotations, the description covers the remaining invocation requirement (connected account) and clarifies the mode switch. The lack of an output schema is a minor gap, but the tool's purpose and return concept are clear from the home-timeline phrasing.

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 100%, with all four parameters explained in the input schema. The description's mention of since_hours restates what the schema already says, so it adds no additional parameter-level meaning.

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 title and description clearly identify the tool as reading the user's home timeline ('Your following feed, newest first'), which distinguishes it from custom-feed and author-feed siblings. However, it does not explicitly name or contrast any sibling tool, so it stops short of full differentiation.

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 gives a concrete usage choice for since_hours versus a fixed post count and states the connected-account prerequisite. It does not provide when-not-to-use guidance or name alternatives such as get_feed or get_author_feed, so the cross-tool routing is left implied.

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