사전규격 복합 검색

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

Annotations provide readOnlyHint and openWorldHint. Description adds significant behavioral context: priority order (specRegistNo > refNo > receipt date), data range (post-January 2025), and parallel search when kind is unspecified. No contradictions.

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?

Description is concise with a single sentence, but it packs multiple pieces of information. It is front-loaded with the main purpose and flows logically. Could be slightly restructured for readability, but overall efficient.

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 (12 parameters, multiple filters), the description covers purpose, usage guidelines, behavioral traits, and parameter context. Missing explicit mention of output format, but for a search tool with no output schema, this is acceptable. Data range and prioritization are well covered.

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?

Schema covers all 12 parameters with descriptions (100% coverage), so baseline is 3. The description adds overall parameter context like priority rules and data range, which aids in selecting parameters but does not elaborate on each parameter individually. This extra context justifies a 4.

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 the tool searches for prespecs with complex conditions using multiple filters (institution, product name, reference number, SW business status). It distinguishes from siblings by explicitly noting that product name search is not supported and directs to search_prespecs_by_product.

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?

Explicitly explains when to use this tool (multiple filters), when not to (product name search), and provides alternative sibling. Also covers priority order and behavior when kind is unspecified.

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