계좌 목록 조회

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

Annotations already mark readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds the concrete return fields (accountNo, accountSeq, accountType) and notes that accountSeq is used as the X-Tossinvest-Account header, plus a current limitation (only BROKERAGE).

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?

Two concise sentences plus a structured return list. No redundant content.

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 no output schema, the description provides the full return structure and usage context. It doesn't cover potential error cases or authentication, but for a 0-param list endpoint, this is 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?

No parameters exist; input schema is empty with 100% coverage, so description adds no parameter detail needed. Baseline 4 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?

Description states '토스증권 계좌 목록을 조회합니다' (retrieve Toss Securities account list), a specific verb+resource. It also explains the returned accountSeq is needed for other API calls, distinguishing its role among sibling 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?

Implies usage before account/asset/order APIs by stating accountSeq is required for those calls. Does not explicitly name alternatives or exclusions, but the context is clear among the sibling list.

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