mayhem_balance

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

No annotations are provided, so the description must carry the burden. It implies a read-only query but does not specify behavior when called (e.g., error on '暫未支援'). The lack of detail on response or side effects reduces transparency.

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 short (two lines) but the first line mixes purpose with a note about not being supported, which could be separated. It is not overly verbose, but the structure could be cleaner.

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?

Despite having an output schema (not shown), the description lacks details about the output format or what happens when the tool is called while not supported. The tool is simple, but the '暫未支援' note suggests incompleteness in functionality, making it less complete.

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?

The description adds valuable context to the 'champion' parameter, specifying it accepts both Chinese and English names (英雄名稱,中英文皆可). This goes beyond the schema's simple type string, and with 0% schema coverage, the description compensates well.

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 queries balance values for ARAM: Mayhem mode, distinguishing it from sibling aram_balance which likely targets normal ARAM. The note '暫未支援' indicates it is not yet functional, which could confuse but does not obscure the intended purpose.

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 guidance on when to use this tool versus alternatives like aram_balance. Does not specify prerequisites or scenarios where this tool is appropriate despite the '暫未支援' warning.

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