advanced_alio_search

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 does not disclose that the tool is read-only, non-destructive, or any other behavioral traits such as rate limits or required permissions. The description only describes functionality, not behavior.

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 sentence with an example, front-loading the key feature '복합 필터 검색'. Every word is informative, and no unnecessary content exists.

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 the complexity (9 parameters, many sibling tools), the description is somewhat minimal. It does not explain how filters combine (AND/OR), default behavior, or output format. The tool has no output schema, so more detail on return values would be helpful.

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 covers 100% of parameters with descriptions. The tool description summarizes the filter categories but does not add new meaning beyond the schema. The example query provides context but does not elaborate on parameter formats or constraints beyond what the schema already states.

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 it is a complex filter search combining category, institution type, ministry, date range, and title keyword. It gives a specific example query ('과기부 산하 K1100 분류 중 최근 1년 개정'), which distinguishes it from other search tools that may not support such multi-filter combinations.

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 this tool is for precise queries with multiple filters, but does not explicitly state when to use it versus sibling tools like 'search_alio_regulation_text' or 'advanced_search'. No exclusions or alternatives are mentioned, leaving the agent to infer usage.

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