Get Stock Quote

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

Annotations already mark readOnlyHint=true, so the description adds minimal behavioral context. It mentions 'real-time market data' but doesn't elaborate on data freshness, latency, or any limitations. No contradictions.

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?

Two succinct sentences: first describes functionality, second provides usage context. No filler words, every sentence serves a purpose. Perfectly concise.

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 tool's simplicity (1 parameter, output schema present, annotations provided), the description covers essential aspects. It could mention output format or limitations, but the existing information is sufficient for correct invocation.

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 100%, and the description adds value by providing examples (AAPL, TSLA) and explaining the parameter's purpose in context. Combined with the schema, the agent has clear understanding of the single required parameter.

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 it retrieves the current stock quote including specific data fields like price, volume, change, and market cap. The verb 'Get' and resource 'stock quote' are explicit. However, it does not explicitly differentiate from sibling tools beyond the name, though the specificity helps distinguish.

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 provides explicit guidance: 'Use this when a user asks about a stock's current price or trading activity.' This directly tells the agent when to invoke. It does not mention when not to use or alternatives, but for a simple read tool, this is adequate.

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