Read a list feed

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

With readOnlyHint and idempotentHint already covering the safety profile, the description adds behavior beyond annotations by specifying newest-first ordering and the list-feed scope. It does not discuss pagination or errors, but the annotation coverage lowers the burden.

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: the first states what the tool returns and its ordering, and the second tells the agent how to construct the required parameter. No filler or redundant restatement.

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 read-only list feed with one required parameter, the description plus schema covers core invocation needs. It does not explain cursor-based pagination or response shape, but no output schema is present and the operation is simple.

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 schema already documents list, limit, and account; the description adds practical sourcing instructions for the required list parameter and clarifies accepted input forms. Cursor still lacks explanation in both schema and description, but the core parameter is enriched.

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 says this returns posts from a curated list in newest-first order, and the title reinforces the action as reading a list feed. The curated-list scope separates it in meaning from sibling feed tools, though it does not explicitly name or contrast them.

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 useful setup guidance by telling the agent to take the list URI from get_pinned_feeds or a bsky.app/lists link. However, it does not explicitly state when to prefer this over similar feed tools like get_timeline or get_feed, or when not to use it.

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