국가 리포트 컨텍스트

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds that it returns refined data for reports, but does not disclose additional behavioral traits such as rate limits, authentication needs, or side effects. It provides some context beyond annotations but is not rich.

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 a single, front-loaded sentence with no extraneous text. Every word contributes to the understanding of the tool's output and configurability.

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 has four parameters, a complete output schema, and comprehensive annotations, the description covers the key aspects: what data is returned and how to customize fields. It does not explain 'refresh' or 'countryCode' in depth, but with annotations and output schema present, it is mostly 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 description coverage is low (25%), but the description mentions that the 'fields' parameter can reduce returned fields, adding value beyond the schema. However, it does not explain 'refresh' or 'sampleSize' meaningfully, leaving some parameters underspecified.

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 returns refined data for reports, specifying the default content (source status, counts, 3 samples per source) and the ability to reduce fields. However, it does not explicitly differentiate from sibling tools like country_humanitarian_context, leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus its siblings, nor are there any when-not-to-use instructions or prerequisites mentioned. The description only states what the tool does, not its appropriate context.

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