get-quote

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

No annotations provided, so description carries disclosure burden. Mentions that for option symbols, response includes Greeks and IV when supported, which is useful. However, does not clarify if tool is read-only, rate limits, or response structure beyond that.

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 short sentences deliver core information efficiently. Front-loaded with main action, no redundant words.

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?

Adequate for a simple one-parameter tool without output schema. Covers basic purpose and a key behavioral nuance. Could be more complete by describing standard response fields (e.g., price, volume) but that is often assumed.

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 already describes the symbol parameter with examples (100% coverage). The description adds meaning by clarifying that option symbol inputs yield additional data (Greeks/IV), which helps the agent understand parameter-dependent behavior.

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?

Verb 'Get' with resource 'latest quote' clearly states the action. Distinguishes from siblings (historical-prices, find-option-expirations, find-options-chain) by focusing on current data for stocks or single option contracts.

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?

Implies usage for obtaining latest quotes but does not explicitly state when not to use or mention alternatives like historical-prices for past data. No direct guidance on tool selection.

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