국가 데이터 상태

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

Description adds concrete details (sources, metrics, cache date) beyond annotations (readOnlyHint, idempotentHint). Discloses that tool summarizes data status and implies caching via 'cache date' wording, though could explicitly mention cache 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?

Single sentence is concise but dense and slightly run-on. Could be broken into clearer bullet points or separated clauses.

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?

Output schema exists, so return values need not be detailed. Description covers main metrics and sources. Lacks mention of refresh parameter behavior and countryCode optionality, but overall sufficient.

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 50% (refresh param described). Description does not explain countryCode parameter or its default/pattern. Fails to compensate for the undocumented parameter.

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 verb 'summarizes' and specific resources (IATI, World Bank, etc.) and metrics (dates, counts, errors, freshness). Distinguishes from siblings like iati_status by aggregating multiple sources.

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 explicit guidance on when or when not to use this tool versus alternatives like iati_status. Does not mention exclusions or best practices.

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