get_markets_short_ratio

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

Discloses default compact summary behavior, detail parameter effect, and filter behavior. Annotations already indicate read-only, so no contradiction. Adds valuable 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?

Well-structured with clear sections, but the Args section is somewhat redundant with the earlier explanation. Still, every sentence adds value and it's logically organized.

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?

Covers purpose, usage, behavior, parameters, alternatives, and return shapes (summary vs full). With output schema present, return values need not be detailed. Complete for a tool with multiple behaviors.

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?

Since schema has 0% descriptions, the description fully explains each parameter: s33 with example, date formats, date_from/to range, detail boolean effect. This compensates entirely for missing schema descriptions.

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?

Clearly states it returns TSE 33-sector short selling ratio, distinguishing it from per-stock short report. Verb 'get' is implied and specific resource is identified.

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?

Explicitly states when to use (sector-level short ratio) and when not (per-stock positions), directing to get_markets_short_sale_report. Also explains behavior with parameters: no params returns summary, filters return full data.

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