download_stat_report

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

Annotations already declare readOnlyHint=true, but the description adds valuable behavioral context: it requires a signature ('서명 필요'), warns about column layout differences per report type to prevent misparsing, and explains the max_rows default as token protection. This goes beyond annotations without contradicting them.

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 concise and well-structured. It starts with the main purpose in the first sentence, immediately followed by a critical warning. Every sentence adds value; there is no redundant or vague language.

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 that an output schema exists, the description does not need to detail return values. It covers the core action, a key behavioral caveat (column layout), and provides an alternative tool. This is complete for a specialized download tool with good annotations and schema support.

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%, so parameters are already documented. However, the description adds meaningful context: it specifies the default for max_rows as 500 with a rationale ('토큰 보호'), and clarifies that download_url comes from 'create_stat_report'. This extra information helps the agent use the parameters correctly.

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 it downloads a StatReport TSV and returns raw rows. It uses a specific verb ('다운로드해') and resource ('StatReport TSV'). Additionally, it distinguishes itself from sibling 'get_performance_report' by noting that for named indicators, that tool should be used instead.

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 states when to use the tool (to download raw stat report TSV) and provides a clear when-not-to-use by warning that column layout differs by report type and advising against interpreting here. It also directs the agent to use 'get_performance_report' for named indicators, offering a concrete alternative.

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