stock_snapshot_trade

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

With no annotations, the description must carry full behavioral disclosure. It only states 'real-time last trade' without mentioning return format, filtering behavior via min_time, venue selection, or any limitations. The minimal wording leaves critical behavioral traits undisclosed.

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 that front-loads the core concept ('Real-time last trade'). It is concise and free of fluff, though it could be structured to include more contextual detail without becoming verbose.

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 absence of annotations and output schema, the description needs to explain what the tool returns and its behavioral nuances. It does not mention that this is a snapshot (single point) rather than a history, nor does it address the min_time filter or default venue. The description is too sparse for an agent to confidently select and invoke this tool.

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%, so the baseline of 3 applies. The description adds no parameter-specific meaning beyond what the schema already provides; it does not mention symbol, venue, or min_time. This meets the baseline but adds no extra value.

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 indicates the tool returns the latest trade for a stock, distinguishing it from sibling snapshot tools like stock_snapshot_quote and stock_snapshot_ohlc. However, it lacks an explicit verb (e.g., 'get' or 'retrieve'), so it doesn't fully meet the standard for a 5.

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 is provided on when to use this tool versus alternatives such as stock_history_trade or stock_at_time_trade. The description offers no context for selecting this snapshot over other time-based or historical tools.

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