get_stock_snapshot

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that analyst consensus is provider-sourced and that insider data is folded in, but it says nothing about latency, rate limits, partial-data behavior, or market coverage (the us/kr enum goes unmentioned).

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 front-loaded sentence that lists the payload contents without a word of filler. Nothing could be cut without losing information.

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 need no explanation here. However, for a two-param tool with an undocumentable 'auto' market default and no routing guidance against 26 siblings, the description leaves real gaps an agent would need to guess at.

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 0% – neither symbol nor market is documented anywhere. The description offers no compensating detail, notably nothing about what "auto" means for market detection or whether symbol format differs between us and kr. Only the word "stock" implies symbol is a ticker, distinguishing it from the crypto siblings.

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 concrete verb ("Return") and resource ("compact stock snapshot") and enumerates the bundled content: quotes, financial metrics, analyst consensus, insider data. That enumeration implicitly distinguishes it from the narrow siblings get_quote, get_key_metrics, and get_insider_trades, but it never says so explicitly.

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?

There is no when-to-use guidance and no named alternative. An agent cannot tell from this text whether to call get_stock_snapshot or to compose get_quote + get_key_metrics + get_insider_trades; only the adjective "compact" hints at a bundled overview.

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