Estimate SkyBlock Net Worth

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

With no annotations, the description carries full burden. It discloses the use of live Bazaar data, optional external BIN source, and returns a breakdown. However, it does not mention rate limits, data freshness, or potential destructive actions (though none expected).

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 moderately long sentence packing much information. It could be more concise or structured (e.g., bullet points). It is front-loaded with the main purpose but could be improved for readability.

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?

Given 13 parameters and no output schema, the description covers inputs well but lacks detailed output structure. It mentions return fields (total, breakdown, top items) but not their types or formats, leaving some ambiguity for an agent.

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 85%, and remaining params have meaningful descriptions. The description adds context like 'use when user gives a name' for username. Default values and enums are well explained, adding value beyond the schema.

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 the tool estimates a profile's net worth from liquid coins, inventory/storage holdings, sacks, and modifiers, using live Bazaar data. It distinguishes from sibling tools like skyblock_profile or skyblock_inventory by focusing on net worth estimation.

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 implies usage for net worth queries but lacks explicit guidance on when to use this tool versus alternatives (e.g., skyblock_profile for profile info, skyblock_bazaar for pricing). No when-not-to-use or context for differentiation is provided.

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