get_quote

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 discloses that the tool is fast and lightweight, and enumerates the returned data fields. For a simple read operation, this is sufficient, though it doesn't mention potential failure modes or authentication.

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?

Three sentences, each earning its place: purpose, return fields, and usage guidance. Concise and front-loaded with the key action.

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?

The description lists the main return fields, compensating for the lack of an output schema. For a simple snapshot tool with one parameter, it is reasonably complete. Could mention any limitations or caching behavior, but not essential.

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?

Only one parameter 'symbol' exists, and schema coverage is 0%. The description does not elaborate on the expected format (e.g., ticker symbol vs. ISIN). Since the parameter name is self-explanatory, it scores a baseline 3, but additional format guidance would improve it.

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 the tool gets a 'fast, lightweight current-price snapshot' and lists specific return fields. It distinguishes itself from the sibling `get_ticker_info`, which is for the full profile.

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?

Explicitly says 'Use this for quick price checks; use `get_ticker_info` for the full profile,' providing clear when-to-use and when-not-to-use guidance with a named alternative.

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