get_character_hyper_stat

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

No annotations are provided, so the description carries the full behavioral burden. The verb '조회' implies a read-only operation, but the description does not disclose any permissions, rate limits, or edge-case behavior. It is not misleading, but it adds only minimal behavioral context.

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, front-loaded Korean sentence with no redundancy or filler. Every word contributes to identifying the tool's purpose, making it highly efficient.

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?

For a simple two-parameter retrieval tool with a full output schema, the description combined with the schema is sufficient for invocation once the agent has an OCID. It lacks explicit usage routing and behavioral depth, but the operation is specific enough that the definition is nearly 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 input schema already documents both parameters (ocid and date) with 100% coverage, including the date format. The description adds no additional parameter meaning, so the baseline score of 3 is appropriate.

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 states exactly what the tool does: '조회합니다' (retrieves) and names the resource '캐릭터 하이퍼스탯 정보' (character hyper stat information). This distinguishes it from sibling tools like get_character_stat and get_character_hexamatrix_stat, which target different stat categories.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites such as obtaining an OCID first. The only usage signal is implied by the resource name, so an agent receives little help in routing to this tool correctly.

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