Server Quality Checklist

Tool Scores

• tojeong_gwae_lookupA
  4.2/5.0
  Behavior3/5

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

  With no annotations, the description bears the transparency burden. It discloses that the lookup returns the exact original text ('그대로 조회') and is auxiliary, implying read-only intent. But it does not mention permissions, return format, error behavior, or side effects, leaving some behavioral aspects unspecified.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is two sentences long, front-loading the core functionality and then stating the intended purpose. Every clause contributes meaning without redundant repetition of schema information.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a simple single-parameter lookup with no output schema, the description adequately covers input format, what is returned (yearly and monthly fortune text), and intended usage. It does not detail response structure or the exact relationship with tojeong_fortune, but given the tool's simplicity and auxiliary role, this is sufficient.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema already covers the parameter with a pattern and example (100% coverage), but the description adds valuable meaning by explaining the code structure ('상1-8·중1-6·하1-3') and range (111~863), which is more intuitive than the regex pattern and aids correct parameter construction.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description states a specific action '조회한다' (retrieves) and a specific resource (the hexagram's total fortune and 12-month monthly fortune original text) using a code format. It also distinguishes itself as an auxiliary tool for browsing/testing/SKILL development, separating it from the sibling tojeong_fortune.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description clearly identifies intended contexts ('browsing, testing, SKILL development') via '보조 도구다'. However, it does not explicitly state when not to use the tool or name the alternative tojeong_fortune, so it lacks explicit exclusions.

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

• tojeong_fortuneA
  4.4/5.0
  Behavior5/5

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

  With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently explains the internal procedure (작괘), the output content (총운 and 12-month monthly fortune), the fact that it returns original text unchanged, and that it does not generate interpretations or use the hour. This is a thorough and honest account of the tool's behavior.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is concise and well-structured: three sentences each serve a distinct purpose—stating the main function, describing the method and return value, and clarifying exclusions. It is front-loaded with the core purpose and contains no redundant words or information.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a tool with no output schema and no annotations, the description does a good job of explaining what it returns and what it does not do. It covers the essential behavior and exclusions effectively. However, it does not mention parameter defaults (e.g., target_year defaults to current year) or provide any guidance relative to the sibling tool, which would round out the context. Nevertheless, the description is sufficiently complete for typical use.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Since the schema description coverage is 100%, all parameters (birth_date, calendar, target_year, is_leap_month) already have clear descriptions. The tool description adds minimal extra meaning: it confirms birth_date as the key input and explicitly states that the hour is not used, which is a helpful clarification but does not significantly go beyond the schema. Therefore, baseline 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool's purpose: it inquires the annual Tojeong Secret fortune based on birth date, computes a 3-digit hexagram, and returns the overall and monthly fortunes as original text. It distinguishes itself from the sibling tool by specifying its input (birth date) and output (fortune text), making it unambiguous.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides clear usage context: it is a data-only tool that returns raw original text and does not generate interpretations or advice, which serves as an exclusion criterion. It also notes that the hour is not used, guiding the user on relevant inputs. However, it does not explicitly mention alternatives like the sibling tool tojeong_gwae_lookup, so it falls short of a full 'when-to-use-vs-alternatives' explanation.

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