도구 발견

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

With no annotations, the description is the only source of behavioral information. It discloses that the tool returns summaries and is a preparatory step for executing hidden tools, but it does not elaborate on side effects, rate limits, or the exact nature of the 'summary'. For a discovery tool, this is adequate but not rich.

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, efficient sentence in Korean that front-loads the action and resource, then adds usage context. Every word contributes value, and there is no wasted detail.

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 no output schema and a single optional parameter, the description adequately conveys what the tool returns and its intended use. It omits a concrete return structure, but the stated purpose is clear enough for an agent to invoke the tool and interpret the result reasonably.

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 description does not discuss the only parameter. However, the input schema fully documents 'includeExposed' with a description and default value, so schema coverage is 100%. Baseline 3 applies because the schema carries the parameter semantics.

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 that the tool returns the name, description, and input schema summary of all registered tools ('등록된 모든 도구의 이름·설명·입력 스키마 요약을 반환합니다'). It also distinguishes itself from siblings by mentioning its role in preparing for hidden tool execution via execute_tool.

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 provides explicit usage guidance: 'Use before calling hidden tools with execute_tool' ('숨김 도구를 execute_tool 로 호출하기 전에 사용하세요'). It gives a clear context but does not mention exclusions or alternatives, though none are apparent among the sibling tools.

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