get_sellable_quantity

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

No annotations are provided, so the description carries the behavioral disclosure burden. It explicitly labels the operation as 'read-only' and clarifies that it returns currently sellable quantity from a single account, adding meaningful behavioral context beyond the name and schema.

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 brief, front-loaded with the core purpose, and includes only necessary parameter details. Every sentence serves a purpose, and the Korean 'read-only' note reinforces without bloating.

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 two-parameter read-only tool, the description covers the operation, parameter provenance, and symbol format. An output schema exists, so return-value documentation is unnecessary. The description is adequately complete for correct invocation.

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 0%, but the description fully compensates by explaining both parameters: account_seq is the numeric value from get_accounts(), and symbol is a single ticker without market prefix with a concrete example. This adds essential meaning beyond the raw schema.

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 states a specific verb ('Get') and resource ('how many shares ... can currently be sold from one account'), making the tool's function immediately clear. It is distinct from sibling tools like get_holdings or place_order, and the account-scoping helps differentiate it from broader market queries.

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 provides clear usage context by specifying that account_seq is the numeric accountSeq returned by get_accounts(), establishing a prerequisite and workflow. It does not explicitly name alternative tools or exclusion cases, but for a simple lookup tool the guidance is sufficient.

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