quote

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

With no annotations, the description carries the transparency burden. It discloses real-time nature, the main outputs, and the secondary behavior of resolving internal company IDs. It stops short of detailing error conditions or data latency, but for a simple quote tool this is adequate.

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 focused sentences, each adding value: the first defines the core function and outputs, the second adds a useful secondary behavior. No unnecessary words or filler.

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 a single parameter, no output schema, and no annotations. The description sufficiently covers what is returned (last price, change, best bid/offer) and the company ID resolution, making it complete for a simple real-time quote tool.

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% and already describes the symbol parameter with examples. The description just repeats 'IDX symbol' without adding new semantic detail, so it provides no significant value beyond the schema.

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 clearly states the tool's purpose: providing real-time quotes for IDX symbols, including specific data points (last price, change, best bid/offer) and the extra function of resolving internal company IDs. It distinguishes itself from siblings like orderbook and intraday_prices by focusing on a snapshot quote.

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 implies usage for obtaining a quick real-time market snapshot and mentions the IDX scope. It does not explicitly exclude alternatives or say when not to use it, but the context is clear enough for a simple quote tool.

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