get_ad_account_info

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

With no annotations provided, the description carries the full burden. It correctly suggests a read-only operation ('조회합니다') without mentioning side effects. For a simple parameterless tool, this is sufficient, though additional details like authentication or rate limits could improve transparency.

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: a single sentence stating the purpose followed by a list of example questions. Every sentence serves a purpose, and the structure is front-loaded with the main action. No wasted words.

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?

For a parameterless tool with no output schema, the description covers the core functionality and the kind of information retrieved (name, status, business info, etc.). It does not detail the return format, but given the tool's simplicity, this is adequate. Slightly higher could be achieved by explicitly stating it returns a single object.

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?

The input schema has no parameters (0 params, 100% coverage trivially). According to guidelines, 0 params gives a baseline of 4. The description does not need to add param info since none exist.

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 the tool retrieves Kakao Moment ad account info (name, status, business info, balance shortage) and provides example user queries. It is specific and distinguishes from siblings like get_bizmoney (balance) or get_performance_report (performance).

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 gives example questions (e.g., 'How is the ad account status?', 'Any balance shortage?') that directly indicate when to use the tool. However, it does not explicitly mention when not to use it or provide alternatives, though the context of sibling tools implies differentiation.

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