Get accounts followed

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals no behavioral traits beyond the basic read operation, such as pagination via cursor, potential rate limits, or whether authentication is required. The description is accurate but fails to add useful behavioral context.

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 sentence that is clear and directly front-loaded. It contains no filler or unnecessary words, and every word contributes to the purpose.

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 relatively simple, but the description omits important context such as pagination (cursor, limit) and does not differentiate from the similar 'get_followers' tool. With no output schema and minimal description, the agent lacks sufficient information to understand response shape or usage boundaries.

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 only 33% (only 'actor' has a description). The description adds minimal semantic value by referring to 'a given user,' which hints at the actor parameter, but it does not clarify the handle/DID format or the omission default. Limit and cursor remain undocumented both in schema and description.

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 'List' and the resource 'accounts a given user follows,' making the tool's purpose unambiguous. It distinguishes itself from the sibling tool 'bluesky_get_followers' by specifying 'following' rather than 'followers.'

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 provides no guidance on when to use this tool versus alternatives. It does not mention the distinction between 'get_following' and 'get_followers' or suggest contexts where this should be preferred.

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