Audit SkyBlock Profile

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

No annotations provided. The description outlines what the tool computes but does not disclose any behavioral traits such as data source latency, authentication requirements, potential errors if profile data is missing, or if external API calls are made. It appears read-only, but no guarantees stated.

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 description is a single, information-dense sentence covering multiple output categories. It is efficient but could be more readable (e.g., bullet points). No wasted words.

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?

No output schema is provided, so the description should hint at return format; it only lists computed items. Also, with 10 optional parameters, there is no guidance on minimal requirements to identify a profile (e.g., uuid or username). The description is adequate but leaves gaps.

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 schema already documents most parameters adequately. The tool description does not add additional parameter-level details beyond what the schema provides, meeting the baseline for high coverage.

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 clearly states 'Return a compact profile audit' and lists specific outputs: computed levels, HOTM/HOTF trees, progression gaps, gear/loadout summaries, accessory analysis, and prioritized next actions. This distinguishes it from sibling tools like skyblock_profile (raw data) and skyblock_networth (net worth only).

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?

No explicit guidance on when to use this tool vs alternatives. It implies a comprehensive audit use case but does not contrast with skyblock_profile, skyblock_networth, or other siblings. No prerequisites or exclusions mentioned.

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