Get sellable quantity

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

The description adds valuable behavioral context beyond the readOnlyHint annotation: it discloses that shares reserved by open sell orders or still settling are excluded, and that the result can be lower than holdings. This is meaningful and non-obvious information that affects how the result should be interpreted.

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 consists of three concise sentences, each serving a distinct purpose: what the tool does, why the value might differ from holdings, and when to use it. There is no irrelevant or redundant text.

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, read-only tool with strong annotations, this description is complete. It covers the purpose, the key behavioral nuance, the return value (how many shares), and the recommended usage context, making it sufficient for an agent to invoke 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?

The schema fully describes the symbol parameter with a clear format and examples, so schema coverage is 100%. The description does not add extra parameter meaning beyond what the schema already provides, so a baseline of 3 is appropriate.

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 returns the number of shares that can be sold right now for a given symbol, using a specific verb and resource. It also differentiates from toss_get_holdings by explaining the quantity can be lower due to reserved or settling shares.

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?

It explicitly says to check this tool before sizing a SELL order, giving a concrete use case. It also names toss_get_holdings as an alternative and explains the difference, helping the agent choose correctly.

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