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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that results are 'published' short positions and describes the returned shape (current, historic, statistics timeseries), which is meaningful context. However, it does not mention rate limits, permissions, data freshness, or pagination behavior — gaps that matter for a data-retrieval tool with zero annotation coverage.

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?

Two compact sentences, zero waste. The first front-loads what the tool returns and the second immediately clarifies the identifier options — ideal ordering for an agent scanning for the right tool.

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 two-parameter read tool with a fully documented schema, the description covers purpose, return shape, and identifier flexibility. It stops short of stating which sibling to prefer or any usage caveats, but no output schema exists and the essential calling information is present.

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%, so the schema already documents both parameters, including format hints like 12-character ISIN and case-insensitive US ticker. The description reinforces that either identifier may be passed but adds no format or constraint details beyond what the schema provides, so baseline 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?

States a specific verb+resource (get short positions of one company) and enumerates exactly what is returned: current positions per holder, historic positions, and statistics timeseries. This clearly distinguishes it from siblings like get_top_short_positions or get_trending_short_positions, which are aggregate/ranking tools rather than single-company detail.

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 says to 'Pass symbol OR isin', which implies it is a per-company lookup and that either identifier works, but it does not explicitly state when to use this tool versus single-company siblings such as get_shortseller_positions or search_companies. Usage is implied by the resource scope rather than stated as explicit when-to-use guidance.

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