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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety and external-data profile is covered by structured fields. The description usefully notes the data is 'real-time' and comes from Yahoo Finance, but says nothing about latency, rate limits, market-hours behavior, or whether a failed symbol returns an error.

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 core purpose is front-loaded in one sentence, and the Args block is compact with no filler. The docstring-style formatting is slightly redundant for an MCP description but costs little.

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?

With no output schema, the description carries the burden of explaining what a 'price quote' returns (last price, change, timestamp, currency?), and it does not. Symbol input is well covered, but the agent cannot predict the shape of the result.

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 0% — the 'symbol' property has no description in the schema — so the description must carry the load, and it does: it gives concrete format examples across asset classes (AAPL, BTC-USD, SPY, ^GSPC, EURUSD=X, THYAO.IS). This is genuinely valuable disambiguation for exotic symbol syntax. It does not state case sensitivity or whether exchange suffixes are required in all cases, so it falls short of 5.

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 states a specific verb and resource ('Real-time price quote from Yahoo Finance') and enumerates the asset classes covered (stock, crypto, ETF, index), which helps separate it from narrow siblings like stock_prices or egx_index_analysis. It stops short of naming a specific sibling it replaces, so it lands at 4 rather than 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?

There is no guidance on when to prefer this tool over alternatives such as stock_prices, market_snapshot, or price_chart, nor any stated exclusions or prerequisites. The agent must infer usage from the name alone.

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