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

Annotations already establish readOnlyHint=true, openWorldHint=true, and destructiveHint=false, and the description correctly does not contradict them. It does add genuinely useful non-schema behavior: credit cost and the warning that repeated identical requests may re-purchase data. However, that cost information is internally inconsistent with a later line, and nothing is said about auth requirements, error behavior for suspended or missing accounts, or 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?

The opening sentence is well front-loaded, but the remainder is boilerplate pricing cruft that reads like scraped page text ("Bluesky Profile API View Pricing Get Bluesky profile info 1 credit per request") and is not even self-consistent. It states the lookup costs "at least 10 Nexscope credits" and then "1 credit per request", which is noise an agent has to reconcile.

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 does the right thing by enumerating the return fields, though the sentence about list/feed-generator/starter-pack counts is garbled. The internal cost contradiction and missing guidance on handle formats leave an otherwise simple one-parameter lookup partially underspecified.

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 100% for the single required parameter ("Bluesky handle"), so the schema already carries the load. The description adds no format detail such as whether a leading "@", a DID, or a bare handle is accepted, so baseline 3 applies.

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 opens with a specific verb and resource ("Retrieves a Bluesky user's public profile") and enumerates the returned fields (handle, displayName, avatar, description, followersCount, postsCount, createdAt, verification status), so the agent knows exactly what it gets. It does not differentiate itself from the very close siblings social_bluesky_post or social_bluesky_user_posts, which is the only thing keeping it from 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 prerequisites (does the profile need to be public? does it accept DIDs as well as handles?), and no mention of the sibling tools that fetch posts for the same account. The cost warning ("Repeated requests may purchase data again") hints at a decision factor but never states when this tool should be chosen over an alternative.

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