bluesky_follows

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: public data, no credentials required, and paginated results ('Returns a page'). This is meaningful transparency beyond what the schema provides, though it omits details like default page size or ordering behavior.

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 two sentences and efficiently conveys the purpose and data source. However, the first sentence 'Accounts a Bluesky account follows.' is redundant with the second, which says the same thing. This slight redundancy prevents a perfect score.

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?

For a simple list tool with fully described parameters and no output schema, the description adequately covers the resource, pagination, and the public, credential-free nature of the data. It does not explain the response shape or default behavior, but these are not critical given the tool's simplicity.

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 already covers 100% of parameters with clear descriptions for actor, limit, and cursor. The description adds no additional semantics beyond what the schema provides, so the baseline of 3 applies.

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 tool returns a page of accounts a Bluesky account follows, with a specific verb ('Returns') and resource ('accounts a Bluesky account follows'). This uniquely distinguishes it from the sibling tool bluesky_followers, which lists the accounts that follow a given account.

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 useful context by noting the data is public and credential-free, implying it can be used without authentication. However, it does not explicitly state when to use this tool versus alternatives like bluesky_followers, nor does it provide exclusions or when-not-to-use scenarios. Usage is implied by the resource description.

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