Get stock metrics

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

Annotations already declare readOnlyHint=true, and the description adds 'Read-only', confirming no side effects. The description details exactly what data is returned, but does not discuss rate limits, data freshness, or authorization requirements. The transparency is good but not exhaustive.

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: two sentences. The first sentence efficiently lists all data categories, and the second provides a critical usage instruction. No redundant or filler content.

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 complexity (multiple metric categories) and the absence of an output schema, the description adequately enumerates the returned data (identity, price, valuation, financials, description). It does not specify data structure or units, but the categories are sufficient for an AI agent to understand the tool's output.

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 100% for the single parameter (ticker), with a clear description. The description adds value by reiterating the ticker format and providing examples (e.g., AAPL, ABBN.SW), which helps disambiguate usage beyond the 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 explicitly states the tool fetches a consolidated metrics snapshot for a single stock by ticker, listing specific categories (identity, price, valuation, financials, description). This clearly distinguishes it from sibling tools like get_financial_history or get_earnings_call_transcript, which focus on narrower aspects.

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 includes a usage guideline to use the exact ticker as listed on Bullrun with Yahoo-style suffixes, providing examples. While it does not explicitly state when not to use this tool or compare to alternatives, the broad snapshot nature implies it is for a quick overview, and the parameter guidance is clear.

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