boj_list_databases

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

With no annotations, the description discloses that 'No API call needed — uses a static list of 40+ databases,' which informs the agent about the tool's lightweight nature and scope. This adds value beyond expectations, though more details like update frequency could improve it.

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 consists of two sentences, front-loading the main purpose and usage instruction without extraneous detail. Every sentence is functional and 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 tool's simplicity (no output schema, optional parameters, static data), the description fully covers its purpose, usage context, and behavioral traits. No additional information is necessary for an agent to use it correctly.

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% with both parameters ('search' and 'category') having descriptions. The tool description adds no extra parameter meaning, so it meets the baseline for a well-documented 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?

The description clearly states 'List all available BOJ statistical databases' with a specific verb and resource. It distinguishes from siblings which are about getting data code, layer, and metadata, making its role as a discovery tool unambiguous.

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 explicitly advises 'Use this first to find the correct DB code before querying data,' providing clear when-to-use guidance. While no explicit when-not-to-use or alternatives are given, the sibling tools are for different purposes, so this is sufficient.

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