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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'public profile,' which hints at a read-only lookup, but it does not mention authentication, rate limits, empty-query behavior, or what the output represents. This is a minimal and insufficient disclosure.

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 very short, but it is under-specified rather than concisely complete. It consists of a single noun phrase with no actionable guidance, so the brevity does not serve the agent's needs.

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?

Although the tool has an output schema, the description still fails to explain the purpose of the single input parameter, the expected query format, or how results relate to the request. For a simple tool this is a significant completeness gap.

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?

The schema describes one parameter, 'q', as a string with a default of '', but the schema description coverage is 0% and the tool description never mentions 'q' at all. An agent has no idea whether 'q' should be a Bluesky handle, DID, URL, or something else, and the description does nothing to compensate for this gap.

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 states the resource domain ('AT Protocol public profile') and identifies Bluesky as the platform, but it contains no verb or explicit action such as 'look up' or 'retrieve'. An agent can infer this is a profile lookup tool, but the wording is vague and does not clearly distinguish it from the many other social-media/profile tools in the sibling list.

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 guidance on when to use this tool versus alternatives like mastodon, medium, or other profile-oriented tools. No context, prerequisites, or exclusions are provided, leaving the agent to guess when this tool is appropriate.

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