List SkyBlock Profiles

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

Annotations already declare read-only, idempotent, open-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: an auth prerequisite (HYPIXEL_API_KEY) and the fact that results are filtered by the player's API privacy settings, which can silently reduce output. It does not describe pagination or output shape, but with no output schema that is a minor gap.

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?

Two tight sentences, no filler. The core purpose leads and the operational constraints follow, so an agent gets the essential facts in the first clause.

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 read-only list tool with no output schema, the description covers purpose, auth, and privacy caveats, and the schema fully documents inputs. It could be stronger by mentioning that profiles are returned compactly vs. the detail tool, but nothing critical for correct invocation is 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 100% – uuid, username, and includeRaw are each documented in the schema, including the 'use this when the user gives a name' routing hint. The description adds nothing about parameter behavior, so the 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 a player's SkyBlock profiles') plus scope ('compact member metadata'), which cleanly separates it from the singular skyblock_profile sibling. It stops short of explicitly naming that sibling or clarifying the profile-vs-detail split, so it falls just below the top tier.

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 gives preconditions (requires HYPIXEL_API_KEY, respects privacy settings) but never says when to pick this over skyblock_profile, resolve_player, or skyblock_audit. Usage is only implied by the resource name.

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