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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), and the description adds genuinely new context: the return shape (text, author, embeds, engagement counts, threaded replies array) and the credit cost model including re-purchase on repeat calls. The cost sentences are muddled and inconsistent ("at least 10 Nexscope credits" versus "1 credit per request"), which weakens rather than clarifies the billing 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?

The first two sentences are well-formed and front-loaded, but the remainder is pasted pricing boilerplate that repeats itself ("cost depends on the operation," "1 credit per request," "actual supplier units are reported per request," "examples are not guaranteed prices") and includes raw UI artifacts like "Bluesky Post API View Pricing Get Bluesky post". The 10-credit and 1-credit statements conflict, so the extra text actively harms comprehension.

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 and a single trivial parameter, the description carries most of the burden and does it reasonably well by enumerating returned fields and the threaded replies array. The gaps are the accepted URL format and behavior on failed/inaccessible lookups; the cost disclosure is present but internally inconsistent.

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?

With one parameter at 100% schema coverage, the baseline is 3. The description adds nothing about URL format — no example such as https://bsky.app/profile/{handle}/post/{rkey} — and the schema's own description is just "Bluesky post URL," so an agent is left to guess the accepted URL shape.

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?

"Fetches a single Bluesky post by URL" gives a specific verb and resource, and the word "single" implicitly separates it from the list-style sibling social_bluesky_user_posts and from social_bluesky_profile. It stops short of naming an alternative tool, so differentiation is inferred rather than stated.

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 implies use when you have a post URL and want its content plus engagement metrics, and warns that "Repeated requests may purchase data again," which is a real usage caution. There is no explicit when-not guidance, no statement about invalid/deleted/private posts, and no reference to the sibling tools an agent could use instead.

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