get_stock_snapshot

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

No annotations are provided, so the description carries the full burden. It mentions 'real-time data' and the fields returned, but it does not disclose behaviors such as data delays, error handling for invalid symbols, rate limits, or whether the data is from a live feed or cached. For a read-only tool with no annotations, this is a significant gap.

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?

The description is a single sentence, clearly front-loaded with the verb and resource, and lists the specific data points concisely. Every word adds value with no redundancy.

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?

Given the low complexity (one parameter, no nested objects) and full schema coverage, the description is reasonably complete. It lists the return fields even without an output schema. However, it omits context like currency or exchange nuances, but for a snapshot tool this is acceptable.

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 has 100% coverage for the single parameter 'symbol' with its description and example format. The tool description adds no additional parameter semantics beyond the schema, so the baseline of 3 applies per the guidelines.

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 what the tool does: 'Get real-time data for a stock' and enumerates specific fields (open, high, low, last price, volume). This distinguishes it from sibling tools like get_chart_data or get_order_book, which focus on different data types.

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 implies the tool is for obtaining a current snapshot of a single stock, but it does not explicitly state when to use it over alternatives like get_chart_data for historical data or get_market_summary for broader market context. No exclusions or alternative guidance is provided, but the purpose is clear enough that an agent can infer usage.

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