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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is fully covered. The description adds only the 'static' qualifier, implying stable/cacheable data, but doesn't spell out that implication or say what happens for an unknown symbol. With annotations doing the heavy lifting, this is a modest addition.

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?

Two sentences with zero filler: field scope first, alternative tool second. Front-loaded and easy to scan.

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?

An output schema exists, so return values needn't be explained, and the description covers scope and the main alternative. It falls just short by not disambiguating against get_ticker_info or mentioning behavior for invalid symbols, but is otherwise sufficient for a simple one-parameter lookup.

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% and the single 'symbol' parameter is documented with an example and case-insensitivity note in the schema itself. The description adds no format, normalization, or error semantics beyond that, so baseline 3 applies.

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 gives a specific verb+resource ('Static metadata of one ticker') and enumerates the returned fields (name, SIC sector, market cap, exchange, employees, listing date), which lets an agent know exactly what it gets. It differentiates from get_ticker_overview, but doesn't distinguish itself from the near-identically named sibling get_ticker_info, leaving a real ambiguity.

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 routes the agent elsewhere for price, recent moves and fundamentals ('use get_ticker_overview'), which is a clear when-not-to-use signal. However, it is silent on when to pick this over get_ticker_info, another metadata-flavoured sibling in the same family.

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