Server Quality Checklist

Tool Scores

• search_precedentsA
  4.4/5.0
  Behavior4/5

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

  No annotations are provided, so the description must carry the behavioral disclosure burden. It mentions using a public API and returning a list of basic information, indicating a read-only operation. It does not discuss rate limits or authentication, but for a search tool, the core behavior is clear and no contradictions exist.

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

  Conciseness4/5

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

  The description is well-organized: a brief purpose statement, then source and output explanation, then a labeled parameter list. Some repetition occurs (serial number usage mentioned twice), but it remains concise and front-loaded with key 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?

  Given 6 parameters, no schema descriptions, and an output schema, the description covers the essential aspects: each parameter, example values, and the output structure. It connects to the sibling tool. However, it could be more complete by clarifying pagination behavior or error handling, but it is adequate for a search tool.

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

  Parameters5/5

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

  Schema description coverage is 0%, so the description fully compensates by listing each parameter with examples and default values. It explains query, max_results, page, sort, org, and date_range with concrete usage hints, adding meaning well beyond the bare schema.

  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?

  Description clearly states the tool searches Korean court precedents by keyword, specifying the source (law.go.kr official API) and the returned information (case name, court, serial number). It explicitly differentiates from sibling get_precedent_detail by indicating that the serial number can be used for detailed lookups.

  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 context on when to use this tool (for keyword-based searches) and implies that get_precedent_detail should be used for full details. It does not explicitly state when not to use it, but the differentiation is sufficient for an agent to understand the tool's role.

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

• get_precedent_detailA
  4.6/5.0
  Behavior4/5

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

  No annotations are provided, so the description carries the full burden. It mentions the official API source, lists return sections (including possibility that some may be missing), and implies read-only behavior. It does not disclose rate limits or authentication, but for a read-only detail retrieval tool, this is adequate.

  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 well-structured: a clear purpose sentence, followed by data source, prerequisite (search), return sections, and parameter details. Every sentence serves a purpose, and the most important information is front-loaded.

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

  Completeness5/5

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

  For a tool with one parameter, no enums, and an output schema, the description provides complete context: how to invoke, what to expect as input and output, and the relationship to its sibling tool. It even notes potential absence of certain return fields.

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

  Parameters5/5

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

  With 0% schema description coverage, the description compensates by explaining the parameter in detail: its meaning ('판례일련번호'), an example value, and how to obtain it ('search_precedents()로 조회한 번호를 사용합니다'). This adds significant value beyond the bare schema.

  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 verb ('조회합니다' - retrieve), the resource ('특정 판례의 상세 내용' - specific precedent details), and the key parameter (판례일련번호/precedent_id). It also distinguishes from the sibling tool search_precedents by noting that the ID comes from search results.

  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 specifies when to use the tool: when a precedent_id is available from search_precedents() results. It explains what it returns but does not explicitly mention when not to use it or provide alternative usage scenarios, though the context with the sibling is clear.

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