dzengi_get_ticker

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

Annotations already mark the operation as read-only and non-destructive. The description adds 'public' and '24-hour' scope but does not disclose rate limits, possible empty results, or formatting behavior. The annotations cover safety, but the description adds only modest behavioral context.

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 sentence that leads with the core action ('Read the public 24-hour ticker') and immediately appends the optional filter. Every word is informative, with no filler or repetition of schema fields.

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 simple read-only endpoint with one optional parameter, the description gives enough to understand the basic call. It is weak on what a 'ticker' contains, what 'normalized' symbol means, and what the response implies when omitted. No output schema exists, so a bit more detail about return shape would help.

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 minimal (only a maxLength constraint), so the description must carry the meaning. It clarifies that the symbol filter is optional and the symbol should be 'normalized', which adds value, but it does not define what normalized means or what symbol formats are accepted.

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 ('Read') and a specific resource ('public 24-hour ticker'), and notes an optional symbol filter. This clearly identifies the operation and distinguishes it from sibling tools like get_candles or get_order_book.

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 makes the use context clear: you call this when you want the public 24-hour ticker, optionally filtered by symbol. However, it does not explicitly state when not to use it or mention alternatives such as get_order_book or get_candles.

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