boj_get_data_code

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

Discloses limits (250 series, 60k points) and error-handling behavior (auto-correction, suggestions). With no annotations, this is adequate but does not mention authentication, rate limits, or idempotency.

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, each serving a purpose: purpose, constraint, error handling. Concise and well-structured.

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?

No output schema, so description should explain return values; it hints at pagination via startPosition but lacks details on response format. For 6-param tool, sufficient but not complete.

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 parameters with descriptions. Description adds cross-parameter constraints (same frequency) and system limits (max 250 codes), going beyond 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?

Description clearly states it fetches time series data by SERIES_CODE, which distinguishes it from siblings like boj_get_metadata (metadata) and boj_list_databases (listing). However, it does not explicitly contrast with boj_get_data_layer.

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?

Implies usage after obtaining metadata codes, and mentions constraints (same frequency, limits). But lacks explicit when-to-use or when-not-to-use guidance compared to sibling tools.

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