get_sellable_quantity

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly marks the operation as 'read-only' and clarifies it only retrieves currently sellable shares, implying no side effects. It does not cover auth or rate limits, but for a simple read query this is reasonably transparent.

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 compact and well-structured: a one-sentence purpose statement is followed by two concise parameter bullets. There is no filler, and the core behavior is front-loaded before the arguments.

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 simple two-parameter read-only query with an output schema present, the description provides the essential information: purpose, read-only nature, account_seq source, and symbol format. Nothing critical is missing for an agent to invoke it correctly.

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%, so the description must fully compensate for parameter documentation. It explains account_seq as the numeric accountSeq returned by get_accounts(), and symbol as a single ticker with no market prefix and an example. Both required parameters are meaningfully documented beyond the bare schema definitions.

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 uses a specific verb and resource: 'Get how many shares of a symbol can currently be sold from one account.' It clearly identifies the operation as a read-only quantity query and distinguishes it from sibling tools like get_holdings, get_buying_power, or place_order by focusing on sellable quantity for a single account.

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 clear usage context: account_seq should be the numeric accountSeq from get_accounts(), and symbol must be a bare ticker without a market prefix. It implies when to use this tool, but it does not explicitly name alternatives or state when not to use it, so it falls short of full routing guidance.

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