Get who an artist follows

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, but the description adds nothing beyond restating the read. It says nothing about pagination behavior, result ordering, or how the followings list is truncated, which matters for a paged list endpoint.

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 single sentence is front-loaded and free of waste, but it is under-specified rather than efficient. Brevity here costs clarity rather than buying it.

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?

An output schema exists so return values need not be explained, but for a three-parameter, paginated list tool with a sibling-heavy namespace the definition leaves too much unsaid: paging, default limit behavior, and the my-vs-user distinction are all missing.

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 'verbose' is documented), so the description should compensate for 'userId' and 'limit'. It adds no clarification on what identifier form userId accepts (string or number) or how limit interacts with paging via next_page.

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 gives a verb and resource ('List the users a user follows'), but the title says 'artist' while the description says 'user', leaving ambiguity about whether this is artist-only or any user. It also never distinguishes itself from the closely related siblings get_user_followers and get_my_followings.

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 when-to-use guidance and no mention of alternatives, even though siblings get_user_followers (opposite direction) and get_my_followings (authenticated user) exist and are easy to confuse with this tool. The agent must infer selection from names alone.

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