Check follow relationships

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context beyond annotations by explaining the return semantics (follow and follow-back status per account) and the one-call batch behavior, with no output schema available.

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 short sentences deliver behavior, batching, and usage guidance with no filler. The core behavior is front-loaded, and every sentence earns its place.

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 two-parameter, read-only tool with strong annotations and complete schema descriptions, the description covers what the agent needs: what is checked, that it handles a whole list, and when to use it. The lack of an output schema is mitigated because the description states the semantic result.

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%, and the schema already documents both parameters well, including account defaults and the list_accounts pointer. The description only reinforces the batching idea behind actors, so it adds little semantic value beyond the schema.

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 first sentence states the exact operation: for each named account, report whether a connected account follows them and whether they follow back. It also distinguishes this from per-profile lookups and sibling list tools by emphasizing a single batch call.

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?

It explicitly says to use this 'before a bulk follow or unfollow rather than reading a profile each time,' giving both a concrete use case and an alternative pattern. The agent can decide when this tool is preferable without further inference.

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