search_blog

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It only states what is searched and does not mention read-only nature, pagination limits, result format, error behavior, or any constraints.

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, concise sentence in Korean with the key action and resource front-loaded. It contains no redundant or filler information, earning high marks for efficiency.

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?

The tool has no output schema and no annotations, and the description provides only the bare purpose. It lacks information about return value structure, pagination behavior, or any usage caveats, leaving the agent with an incomplete picture for successful invocation.

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 provides descriptions for all four parameters (100% coverage), and the description adds no extra meaning about sort, start, display, or query semantics. This meets the baseline but does not enhance understanding beyond the schema.

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 identifies the tool as a Naver blog search ('네이버 블로그 검색') with a specific content focus (real reviews, personal experiences, tutorials). This verb+resource formulation distinguishes it from sibling tools like search_news or search_cafearticle.

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 implies usage for finding blog posts in Naver, but provides no explicit when-to-use guidance, exclusions, or alternative tool mentions. The intended use case is only inferred from the resource and content description.

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