get_markets_short_sale_report

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

Annotations already indicate read-only, idempotent behavior. The description adds that positions are disclosed weekly per institution, which provides helpful frequency context beyond annotations.

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 well-structured with a one-line summary, usage guidance, and parameter details. It could be slightly more concise by reducing redundant Japanese translations, but overall it is efficient.

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 5 optional parameters and an output schema, the description fully explains parameter semantics, provides usage context, and differentiates from siblings, making it complete for an AI agent.

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?

With 0% schema description coverage, the description compensates by explaining each parameter in the 'Args:' section, including format examples and purpose (e.g., 'code: Stock code (5 digits, e.g. 27800)').

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 'Per-stock institutional short sale positions' and provides Japanese translations, making the purpose explicit. It distinguishes itself from sibling 'get_markets_short_ratio' which covers sector-level ratios.

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 explicitly lists use cases ('short squeeze screening') and provides pairing guidance with 'get_equities_earnings_calendar' and an alternative for sector-level data, giving clear when-to-use and when-not-to instructions.

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