bdtick

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

With no annotations, the description must disclose behavioral traits. It only says 'Get Bloomberg tick data', omitting critical details such as whether data is real-time, rate limits, required permissions, or the structure of the response.

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 very concise at four words. However, conciseness is not valuable if it comes at the expense of clarity. A few more words could greatly improve utility without becoming verbose.

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?

The tool has 6 parameters, 2 required, no output schema, and no annotations. The description is far too minimal to cover these needs. It fails to explain what tick data is, how parameters interact, or what the return value looks like.

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 should explain what each parameter means. No parameter descriptions exist, and the description 'Get Bloomberg tick data' adds no context. Parameters like 'time_range' and 'kwargs' remain ambiguous.

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 states 'Get Bloomberg tick data', which clearly identifies the action (get) and resource (Bloomberg tick data). However, it does not differentiate from sibling tools like bdh (historical) or bdp (reference), which could overlap.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of the data granularity, use cases, or conditions that would make bdtick the appropriate choice.

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