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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the data source (Yahoo Finance) and scope (individual ticker symbols) but does not disclose other behavioral aspects like rate limits, data latency, or error handling. This adds some value but not rich context.

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 two sentences plus a short use-case sentence. It is front-loaded with the main purpose, lists useful data fields, and provides guidance. Every sentence earns its place without unnecessary verbosity.

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 compensates by listing the specific data fields returned. It covers purpose, data content, and use cases. It could mention single-ticker limitation or potential errors, but for a simple one-parameter tool, it is quite complete.

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% with a well-described ticker parameter including examples. The description does not add additional parameter semantics beyond confirming it handles individual ticker symbols. Baseline of 3 is appropriate given the schema handles the parameter documentation.

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 comprehensive stock market data for individual ticker symbols from Yahoo Finance. It lists specific data fields, distinguishing it from siblings like get_crypto_prices or get_exchange_rates.

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 use cases: 'Use for fundamental analysis, stock screening, or building financial dashboards.' It does not explicitly state when not to use it (e.g., for crypto or exchange rates), but the individual-ticker focus and sibling names imply this.

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