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

The annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds no additional behavioral context—no mention of return format, error handling, rate limits, or what happens with invalid handles. Since the description carries minimal weight and annotations cover the essential traits, this is adequate but not enriched.

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 description is a single, efficient sentence. It is front-loaded with the primary action and resource, with no wasted words. It earns full marks for conciseness.

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?

Given the tool has one parameter, no output schema, and simple read-only annotations, the description is minimal but not fully complete. It does not explain what profile data is returned (e.g., handle, display name, bio) or any error behavior. For a simple lookup, this may suffice, but the lack of detail on return value leaves some ambiguity.

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%, so the schema already fully documents the 'handle' parameter, including the option to have or omit a leading @. The description's statement 'Accepts a handle' is redundant with the schema and adds no new semantics. It meets the baseline for high schema coverage.

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 clearly states the verb 'Get' and the resource 'Bluesky profile', specifying it is for a creator or account. This distinguishes it from siblings like bluesky_post_get and bluesky_profile_posts_list. The phrase 'for a creator or account' adds slight redundancy but ensures the scope is understood.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. However, the clear resource and platform in the name make the intent obvious, and the sibling list includes related post/list tools that are implicitly different. There is no direct guidance on when not to use it, so it earns a midpoint score.

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