stocks_get_snapshot

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

No annotations are present, so the description bears full responsibility for disclosing behavior. It reveals the response contains a combination of minute/day/previous-day aggregates and last trade/quote, which is useful, but it does not mention whether data is real-time/delayed, what happens if the symbol is invalid, or any access/rate-limit requirements.

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?

One sentence with a front-loaded verb and a compact parenthetical list of content. No wasted words; 'agg' is terse but acceptable given the domain.

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 one-parameter tool with no output schema, the description lists the key response components (minute, day, prev day aggregate, last trade/quote), giving the agent a reasonable sense of what to expect. However, it does not provide enough detail about response structure, data timing, or edge cases, so it is not fully complete despite the low complexity.

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 input schema has a single `symbol` field with no description, and schema coverage is 0%. The description only implies the symbol refers to a stock ticker via 'for a stock', but does not specify format, case, or examples. It adds minimal meaning beyond the schema's parameter name.

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 ('Get') and resource ('current snapshot for a stock'), and the parenthetical enumerates included data: minute, day, prev day agg, last trade/quote. This clearly distinguishes from sibling tools like stocks_get_last_trade or stocks_get_snapshot_all because it is the singular-stock aggregate snapshot.

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?

No guidance on when to choose this over sibling tools. It does not mention alternatives such as stocks_get_current_price or stocks_get_aggregate_bars, nor state when this snapshot is preferred. The use case is implied but not explicitly compared with other tools.

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