search_key_indicators

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

No annotations are provided, so the description must disclose behavioral traits. It does not state whether the tool is read-only, any side effects, authentication needs, or rate limits. The return format is described, but not operational 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 well-structured with Args and Returns sections, and each parameter is clearly explained. It is not overly verbose, though some redundancy in Korean text could be trimmed. Still, it is mostly concise.

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 absence of annotations and the presence of an output schema (which we don't see but is noted), the description provides a good overview of inputs and the return format. However, it lacks behavioral context and does not mention prerequisites or error cases, which are needed for full completeness.

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 description fully explains all four parameters: by (with enum values), value (with context-dependent meaning), page, and limit. It provides enough detail for an agent to correctly populate them, compensating for the 0% schema description coverage.

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 that the tool searches KOSIS statistical key indicators by name or unique ID. It provides specific endpoints and distinguishes itself from sibling tools like search_statistics by targeting key indicators specifically.

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 explains the two search modes (by name or ID) and their parameters, but does not explicitly state when to use this tool versus alternatives like browse_categories or search_statistics. No 'when not to use' guidance is provided.

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