Short Trades

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

Annotations already indicate readOnlyHint=true, etc. The description adds transparency by detailing the data sources (FINRA/NASDAQ for US, HKEX for HK) and the specific fields returned for each market, which goes beyond what annotations provide and helps set expectations.

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 at four sentences, with the main purpose front-loaded. Every sentence adds value, and there is no redundant or extraneous information.

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 the presence of an output schema, the description covers all necessary aspects: purpose, parameters with examples, return field breakdown by market, and data sources. It is complete and leaves no major gaps.

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%, but the description adds practical usage notes like 'omit for latest' for last_timestamp and the default for page_size, which are not fully captured in the schema descriptions. This provides additional semantic clarity.

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 starts with 'Get daily short-sale volume history for HK or US stocks', clearly stating the verb (get), resource (short-sale volume history), and scope (HK or US stocks). It also specifies that market is inferred from symbol suffix, which helps differentiate from 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?

The description provides usage context for parameters, such as 'last_timestamp: unix seconds (omit for latest)' and 'page_size: 1–100 (default 20)', and explains the data structure for each market. However, it does not explicitly state when to use this tool versus alternatives, leaving some ambiguity.

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