fiscal_search

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

No annotations provided, so description carries burden. It mentions the search returns results with 'code' but does not specify response structure, pagination, or error handling. However, it provides enough context for agent to understand it's a search/discovery step.

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?

Three sentences, no fluff. Front-loaded with purpose, then usage instruction, then concrete example. Every sentence adds value.

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 no annotations, the description is self-contained for a search tool that feeds into a sibling tool. The example bridges the gap, making the workflow complete. No return type explanation needed as it's meant to be interim.

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 coverage is 100% and description enriches parameters with examples (keyword: '국가채무') and explicit enum values with translations. The category descriptions and enum values are well explained in schema, but description adds workflow context.

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?

Description clearly states it searches '열린재정 API' by keyword or category, specifying the resource and action. It differentiates from siblings by instructing to check 'code' and then call fiscal_query for data retrieval.

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 states when to use (to search and find a code) and when to use fiscal_query instead (to fetch data with the code). Provides an example workflow with fiscal_search → code → fiscal_query.

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