Harga saham terkini

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description goes further by warning that prices may be delayed from the exchange and that a freshnessNote (market status and data timestamp) must be surfaced to the user. It also clarifies this is informational, not a buy/sell recommendation. No error or rate-limit behavior is described.

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?

Front-loads the purpose, then inputs, then required output behavior and the informational disclaimer. Every sentence carries actionable weight (returned fields, freshnessNote obligation, data caveat) with no 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?

For a single-parameter read tool with no output schema, the description adequately covers inputs, returned fields, and freshness semantics. Minor gaps remain on error behavior for invalid or delisted tickers and on whether index codes need any special format.

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 100% and the single 'ticker' parameter is already documented as 'Kode saham IDX, mis. BBCA atau IHSG'. The description's examples (BBCA, BBRI, TLKM, IHSG) largely duplicate that, so the baseline of 3 applies with no meaningful value added.

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 and resource in Indonesian ('Ambil harga terakhir saham Bursa Efek Indonesia'), and enumerates what it returns: last price, daily change, 52-week range, and price per lot (100 shares). The word 'terakhir' (latest) implicitly separates it from the sibling get_history, and the explicit support for the IHSG index adds scope clarity.

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?

Gives example tickers (BBCA, BBRI, TLKM, IHSG) and instructs the agent to always relay freshnessNote, which implies usage context. However, it never states when to choose this tool over get_history, compare_stocks, or get_portfolio, so routing guidance is left to inference.

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