get_hero_details

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

No annotations are present, so the description carries the full burden. It discloses fuzzy matching behavior, case-insensitivity, and accepted input forms, and details the return structure. It does not mention error behavior or rate limits, but for a simple read-only lookup this is fairly transparent.

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 well-structured with 'Use this when', 'Supports', 'Args', 'Returns', and 'Examples' sections. It is appropriately detailed (about 200 words) with no redundant fluff; every sentence adds value.

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 tool's simplicity and the presence of an output schema, the description is complete for typical use. It covers usage, parameter semantics, examples, and return fields. It doesn't address edge cases like unknown heroes or partial matches, but fuzzy matching is explained, so this is a minor gap.

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 coverage is 0% and the schema only declares 'hero' as anyOf integer/string with no description. The description fully compensates by explaining accepted formats (display name, internal name, fuzzy match, ID) with concrete examples, making parameter semantics crystal clear.

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 'Get detailed hero information by hero name or ID with fuzzy matching', which is a specific verb+resource+method. It distinguishes itself from sibling tools like get_item_details and get_aghs_details by focusing on hero data.

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?

Provides explicit 'when to use' guidance with example user queries ('Use this when users ask about heroes: ...'). However, it does not mention explicit exclusions or alternative tools for hero-specific queries (e.g., get_hero_matchups), so it lacks the full 'when-not-to-use' component.

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