Google Finance Quote

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds genuinely new behavioral context: Google imposes rate limits, rapid repeats risk blocking, and blocked results require waiting or an alternative tool. That's real operational guidance beyond the annotations.

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?

Three short, front-loaded blocks: purpose, ticker syntax, rate-limit caveat. No wasted sentences, though the mixed Indonesian/English phrasing adds mild reading friction.

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?

An output schema exists so return values needn't be described. With that covered, the description supplies the missing input-format guidance and the rate-limit behavior. Main residual gap is not clarifying its relationship to the overlapping google_fx_rate sibling.

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 0%, so the description must carry the load, and it does: it explains ticker format with concrete examples per exchange ('BBCA'+'IDX', 'AAPL'+'NASDAQ') and forex pair normalization ('USD-IDR', 'USDIDR/USD/IDR' accepted). It leaves 'hl' and 'exchange' defaults unmentioned, hence not a 5.

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+resource ('Scrape Google Finance quote') and enumerates covered asset classes (stocks, forex, crypto). It's clear what it does, though it doesn't explicitly distinguish itself from the sibling google_fx_rate, which presumably overlaps on forex quotes.

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?

Provides a useful rate-limit workaround ('wait or switch to an RSS-based tool'), which is a strong when-blocked alternative. But it never states when to use this over google_fx_rate for currency pairs, leaving sibling routing ambiguous.

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