List connected accounts

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds context that these are accounts the server can act as, and the handles are to be used elsewhere. No contradictions or hidden side effects implied.

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?

Three sentences, each purposeful: what it does, how to use its result, and when to call it. No filler or redundancy.

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?

The tool is simple, with no parameters and no output schema. The description covers purpose and downstream usage, but doesn't specify the exact return structure (e.g., whether profile data is included beyond the handle). Still, all essential information for correct invocation and follow-up is present.

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?

No parameters exist, so the baseline is 4. The description mentions the `account` argument used elsewhere but doesn't need to describe parameters for this tool itself.

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?

States a specific verb 'List', a resource 'Bluesky accounts', and scope 'every...server can act as'. It clearly distinguishes itself from siblings by being the only account enumeration tool, and explains that it returns handles used as account arguments.

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?

Explicitly instructs to call this first when the user has multiple accounts and hasn't specified which one, and explains how the handle integrates with the `account` argument of other tools. This provides clear conditions and routing guidance.

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