use_account

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

With no annotations, the description carries the full burden. It discloses the primary behavior (setting a session-level default) but does not mention potential side effects, error conditions, whether authentication is required, or how the session state is managed. The description is not misleading, but it is minimally informative beyond the basic action.

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, concise Korean sentence: '이후 조회의 기본 대상 광고계정을 세션에 설정.' It is front-loaded with the action and resource, and every word contributes meaning. No filler or redundancy.

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 single-parameter setter tool with an output schema, the description is adequately complete. It explains the session context and the effect on subsequent lookups. It does not elaborate on session lifecycle details, but given the tool's simplicity and the presence of sibling session management tools, this is acceptable.

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%: the only parameter ad_account_id has a description '이후 조회에 사용할 광고계정 ID' that fully explains its meaning. The tool description adds no new detail about the parameter, so the baseline of 3 applies.

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's function: setting the default advertising account for subsequent lookups in the session. The verb '설정' (set) and resource '기본 대상 광고계정' (default target ad account) are specific, and the context '세션' (session) distinguishes it from account listing or retrieval tools.

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 implies its usage context: it should be called before performing lookups that need an account context. It clearly states the effect on subsequent queries, providing clear context. However, it does not explicitly mention exclusions or alternatives, though none are clearly needed given its unique role among siblings.

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