Get a student's fan club

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

Annotations already declare readOnlyHint/openWorldHint, but the description adds a trait annotations cannot express: the returned text is authored by third parties, is untrusted, and must be treated as data rather than instructions. That is a concrete, actionable behavioral disclosure for an open-world read.

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, each load-bearing: what it returns, where the parameter comes from, and how to treat the output. The safety caveat is placed last, after the operational facts, which is the right ordering.

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?

With only one required parameter and no output schema, the description covers everything an agent needs: the return contents, the parameter source, and the trust posture of the response. Nothing material is left unstated.

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 100% and the single artist_id parameter is documented with a format pattern in the schema. The description adds the sourcing hint (fetch it from artsonia_list_students), which is mild extra value, but it does not add format or constraint detail beyond the schema — baseline 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?

States a specific verb and resource ('List the fans ... in a student's fan club') and even names the shape of the result (name + relationship). This clearly separates it from write-oriented siblings such as artsonia_invite_fan and from the comment/feedback tools.

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?

Gives an explicit prerequisite: 'Pass the artist_id from artsonia_list_students,' which tells the agent how to obtain the required input and which sibling to call first. There is no explicit when-not guidance, but the read-only listing context is clear.

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