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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context—newest-first ordering, page-based retrieval, and the presence of engagement counts and media attachments—but says nothing about pagination mechanics, cursor behavior, or authentication needs.

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?

A single efficient sentence with the resource front-loaded and the return contents tacked on usefully. No wasted words, though it is short enough that the missing parameter and pagination detail is conspicuous.

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?

An output schema exists, so return values do not need explaining. However, for a paginated, parameterized feed with 0% schema coverage, the description leaves cursor/limit semantics and the requirement to page through results unstated—an agent calling this correctly would need to guess.

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%, so the description must carry the burden for actor, limit, and cursor. It only loosely implies what actor means ("an account's posts") and gives no meaning for limit or cursor, leaving two of three parameters entirely undocumented.

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?

States a specific resource (a Bluesky account's posts) and a clear scope (a page, newest first) plus what each item contains. It is clear what the tool returns, but it does not distinguish itself from sibling feeds like bluesky_posts or bluesky_post_thread, so it falls short of a 5.

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?

There is no when-to-use guidance, no mention of alternatives such as bluesky_posts or bluesky_search_actors, and no conditions described for selecting this tool over the others in the Bluesky family.

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