quote

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds useful behavioral detail by specifying the output components and the side-effect-free resolution of an internal company id, which is beyond what annotations convey.

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 concise sentences with no filler. The primary purpose is front-loaded, and the secondary behavior (internal company id resolution) is appended as a short, useful note.

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 one required parameter, no output schema, and simple read-only behavior. The description lists the key returned fields and the extra resolution behavior, which is enough for an agent to call it correctly. It does not discuss error cases or invalid symbols, but these are not critical for a low-risk quote endpoint.

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?

The schema provides 100% coverage for the single required symbol parameter, including an example ('BBRI') and the IDX/index distinction. The description itself does not add much parameter-level detail, but the schema carries that weight adequately.

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 provides a real-time quote for an IDX symbol, listing exactly what is returned: last price, change, and best bid/offer. It also mentions the additional behavior of resolving the symbol's internal company id. This differentiates it from siblings like orderbook or price_chart.

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 gives clear usage context: use this when a current quote snapshot for an IDX symbol is needed. It implies this is not the tool for order depth, historical charts, or fundamentals, though it does not explicitly name alternatives or exclusions.

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