Get an artist's followers

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing further: no pagination behavior (despite a limit parameter and a next_page sibling), no note that results are publicly available, and no indication of result ordering.

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?

A single sentence with no padding, which is good, but the brevity comes at the cost of under-specification rather than efficiency. Nothing is front-loaded because there is nothing beyond the bare 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?

An output schema exists, so return values need not be explained, but the description omits pagination behavior and the identity/format of the required userId — both essential for correct invocation among this dense set of follower-related siblings.

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 coverage is only 33% — only 'verbose' is documented, and that documentation lives in the schema, not the description. The description says nothing about userId (whether it accepts an artist ID, username, or permalink) or the limit bounds/default, so it fails to compensate for the coverage gap.

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 and resource ('List the users who follow a user'), so the agent knows it retrieves a follower collection. It does not distinguish this from near-identical siblings such as get_user_followings or get_my_followers, and the title's 'artist' conflicts slightly with the description's 'user'.

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 guidance on when to use this instead of get_user_followings (reverse direction) or get_my_followers (authenticated user). The agent must infer the distinction from sibling names alone.

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