get_quote

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

No annotations are provided; the description carries full burden. It discloses a 5-minute data delay and explains the return fields (last price, change, volume, etc.), giving a complete picture of behavior.

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 concise with four clear sentences covering purpose, parameters, returns, and note. Every sentence 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 tool's simplicity (one parameter, no output schema, no nested objects), the description fully covers parameter usage, return details, and data delay. No gaps remain.

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?

Input schema has 0% description coverage, but the description defines the 'symbol' parameter with concrete examples (e.g., 'MEBL', 'OGDC'). This adds essential meaning beyond the raw schema.

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 retrieves a current price quote for a PSX-listed symbol, specifying the resource and scope. It distinguishes from siblings like get_indices and get_market_status.

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 usage with examples (e.g., 'MEBL', 'OGDC') and context (PSX). It lacks explicit when-not-to-use or alternative tools, but the context is sufficient for correct selection among siblings.

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