get_intraday_ticks

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

No annotations exist, so the description carries the full burden. It discloses that output is high-volume and that the window should be constrained, which is useful behavioral context, but says nothing about permissions, rate limits, or whether the call is expensive/quota-limited beyond the volume warning.

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?

Purpose and the volume warning are front-loaded and the Args block is compact. The Args restate parameter names already present in the schema, but the added semantics (formats, enum values, defaults) earn their space.

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?

An output schema exists, so return-format explanation is unnecessary, and the description covers all parameters plus the key operational constraint. It leaves gaps on sibling selection (bars vs ticks) and auth/quota behavior, but is otherwise sufficient for correct invocation.

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 0%, so the description must compensate, and it largely does: it documents all four parameters, specifies ISO-8601 UTC for the datetimes, and enumerates valid event_types values plus the TRADE default. Only 'security' stays thin ('A single Bloomberg ticker') without noting format conventions.

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 ('Tick-by-tick data for a single security') and names the underlying BLPAPI request, which is informative. It does not explicitly distinguish itself from the sibling get_intraday_bars, an agent must infer the granularity difference.

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?

Provides a real usage caveat ('Keep the window short - ticks are voluminous'), which is genuinely actionable. However it never says when to prefer this over get_intraday_bars or what a 'short' window practically means, so the guidance is implied rather than explicit.

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