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 a useful cost signal ('1 credit') and the shape of returned data, but says nothing about failure modes such as nonexistent, suspended, or private handles.

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?

One compact sentence plus a cost tag – nothing wasted and the field list is front-loaded. Slight redundancy in restating 'Bluesky profile' when the tool name already says it, but that is a minor cost.

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, listing the returned fields is genuinely valuable and largely fills the gap. However, for an open-world read tool it omits accepted handle formats and behavior for invalid or private accounts, leaving the definition only minimally sufficient.

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% and there is a single required handle parameter with an example, so the schema already carries parameter meaning. The description adds no format detail (e.g. whether '@' prefixes or DIDs are accepted) beyond the schema.

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?

Names the resource (Bluesky profile) and enumerates the concrete fields returned (bio, avatar, followers, following, post count), so an agent knows exactly what it will get. There is no explicit verb and no direct mention of the sibling bluesky_user_posts or bluesky_post, but the name-plus-field-list makes the purpose unambiguous.

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 gives no when-to-use guidance, no prerequisites, and never contrasts this with bluesky_post or bluesky_user_posts. An agent must infer from the name alone that this fetches profile metadata rather than posts.

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