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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that results are 'public posts' and that a cursor enables pagination, which is useful context. It does not state whether results are ordered by time, how pagination terminates, or any rate limits.

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?

Only two sentences, but the second restates the uri definition already present in the schema and ends with a garbled clause ('to retrieve look up Bluesky posts in a batch') that weakens the sentence. Purpose is reasonably front-loaded, but the redundant and unpolished trailing text costs points.

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 read-only paged list endpoint with full schema coverage, an output schema, and safety annotations, the definition covers purpose and pagination adequately; the output schema handles return values. The only shortfall is the missing routing detail among the several bluesky_post_* siblings.

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 coverage is 100%, so uri, limit, and cursor are already documented in the schema. The description restates the uri meaning verbatim and echoes cursor pagination without adding format or range details. Baseline 3 is appropriate when the schema carries the parameter burden.

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 verb and resource: 'Returns public posts that quote the specified post'. An agent can distinguish this from the analogous siblings bluesky_post_likes and bluesky_post_reposted_by by the 'quote' relationship. No explicit sibling contrast beyond the awkward bluesky_posts mention, so not a full 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?

Only guidance is 'Use bluesky_posts to retrieve look up Bluesky posts in a batch', which is grammatically garbled and only loosely related to this tool's input. It does not clarify when to choose this over bluesky_post_likes, bluesky_post_reposted_by, or bluesky_post_thread, and gives no exclusion conditions.

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