Audit SkyBlock Profile

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that output is a compact/computed summary (useful vs. a raw dump) but says nothing about data freshness, caching, rate limits, or upstream API dependencies, which matters for an openWorld tool.

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?

One dense sentence with no filler; the verb and the return payload are front-loaded. It is essentially a comma-separated content list, which is efficient but borders on enumeration rather than prioritizing the most decision-relevant output.

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 no output schema, the description usefully enumerates the return sections, which is the main burden it must carry. However, for a 10-parameter tool it never explains how uuid/username/profileId/memberUuid interact, nor does it address data recency or that results are derived from upstream sources.

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 80%, so the baseline of 3 applies; the description references no parameter at all, including the significant `focus` list that shapes the audit. Two params (includeMayor, includeEconomy) are undocumented in both schema and description, so no compensation is provided.

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 ("Return a compact profile audit") and enumerates the concrete derived contents: computed levels, HOTM/HOTF trees, progression gaps, gear/loadout summaries, accessory analysis, and prioritized next actions. This implies a computed analysis rather than the raw data served by skyblock_profile, though no sibling is named explicitly.

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, no condition distinguishing it from skyblock_profile, skyblock_upgrade_advisor, or skyblock_networth, and no stated prerequisites (e.g., that a resolvable player/profile is needed). The audit framing implies usage but nothing is stated.

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