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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds no further behavioral context such as authentication needs, rate limits, or what happens if the id is invalid; it only restates the retrieval action.

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 sentence with no redundancy or filler. For a simple retrieval tool, this is an appropriately sized statement.

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?

While the description indicates what data is returned, it leaves the only required parameter undocumented and gives no usage context relative to siblings. With no output schema and no parameter description coverage, an agent lacks enough information to invoke the tool correctly in ambiguous situations.

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 sole required parameter 'id' has 0% schema description coverage, and the description does not mention it at all. There is no explanation of what the id refers to, its format, or how to obtain it, so the description fails to compensate for the missing schema 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 names a specific verb ('조회합니다' / retrieves) and resource ('사이트의 이용 조건, 기능, 확인 출처와 날짜' / a site's usage conditions, features, verification source and date). It is clear what the tool does, but it gives no indication of how it differs from siblings such as get_site_guide or search_sites.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when-not-to-use cases, or any of the sibling tools that might return overlapping site information.

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