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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: newest-first ordering, the default exclusion of reposts with a rationale, and a stated cost of 1 credit. It stops short of describing result shape or pagination behavior.

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?

Four short sentences, front-loaded with the core purpose and no filler. The opening 'User posts.' duplicates the title and could be dropped, but the remaining content is dense and 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?

With no output schema, the description carries the burden of describing what comes back, and it does not — no indication of post fields, media handling, or how pagination terminates. Annotations and the schema cover safety and half the parameters, so this is adequate but with a clear gap for a listing tool.

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 60% — handle, cursor and include_reposts are documented in the schema. The description usefully explains the *why* behind include_reposts defaulting to false, but says nothing about count, cache_max_age, or the format of the cursor value, leaving part of the coverage gap unfilled.

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+resource: 'Recent public posts from a Bluesky account, newest first.' An agent can distinguish this listing tool from the single-post sibling bluesky_post, though no sibling is named explicitly. The leading fragment 'User posts.' merely restates the title and adds nothing.

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?

Usage is only implied — fetch a feed of an account's own writing. There is no explicit when-to-use versus bluesky_post, bluesky_profile, or other userPosts siblings, and no stated preconditions (e.g., private/suspended accounts).

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