get_augment

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions fuzzy search and locale but omits whether the operation is read-only, pagination behavior, error handling, or any limitations. For a search tool this is insufficient 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 relatively concise and front-loaded with purpose. The args section is clear, though including examples adds length. It efficiently conveys key info without being verbose.

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 the existence of sibling tools and an output schema, the description sufficiently covers what the tool does and how to use it. It could be more complete with notes on result limits or behavior, but overall adequate.

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?

With 0% schema description coverage, the description adds essential meaning: it explains 'query' can be Chinese/English keywords with examples, and 'locale' specifies response language. This goes beyond the bare schema types.

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 it performs fuzzy search for Arena hex augments and returns name, rarity, and effect. This specific verb-resource combination distinguishes it from siblings like list_augments (exact list) and aram_balance/mayhem_balance (different game modes).

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 explains the tool's function and provides example queries, implying when to use it (fuzzy search for augments). However, it does not explicitly state when not to use it or contrast with siblings, leaving some inference to the agent.

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