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

With no annotations, the description carries the full behavioral burden. It does disclose the ranking semantics (magnitude of net short position change, over 7D or 28D) and that both increase and decrease directions exist, which is useful. It says nothing about result size, ordering, pagination, or that this is a read-only listing, so significant gaps remain.

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?

A single dense sentence with the core ranking concept front-loaded and no filler. The trailing parenthetical '(home page trend lists)' is the only slightly noisy element, and it does convey source context.

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 3-required-param tool with no annotations and no output schema, the description covers the ranking concept and two of three parameters but omits region entirely and gives no sense of return shape or result limits. Adequate but with clear 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 description coverage is only 33% (only direction is documented in-schema). The description maps the timeFrame enum to human terms ('7 or 28 days') and echoes direction ('increase or decrease'), adding real value for two of three params. The region parameter (EU/US) is never mentioned anywhere, so the description does not fully compensate for the coverage gap.

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 names a specific resource (companies' total net short position) and a specific ranking criterion (largest move over 7 or 28 days), which implicitly separates it from get_top_short_positions (largest position) and get_recently_updated_positions. It never explicitly names those siblings, so an agent still has to infer the boundary.

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 parenthetical '(home page trend lists)' gives some usage context, implying this is the tool for trend/momentum views. There is no explicit when-to-use versus when-not-to-use guidance and no alternative tool is named, leaving the choice against the five sibling position tools to inference.

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