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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds behavioral context by enumerating the returned metadata fields (name, sector, industry, etc.) and framing the operation as quick, which informs the agent about expected output scope and lightweight nature.

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 consists of two concise sentences: the first states the core function and output fields, the second offers a usage tip. Every word earns its place with no redundancy, making it optimally front-loaded and readable.

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?

For a simple one-parameter read-only tool, the description covers the essentials: what it does, what fields it returns, and when it is useful. The lack of an output schema is partially mitigated by the listed fields, though the exact response shape remains unstated. The tool's simple nature and clear annotations make this acceptable.

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% since the only parameter 'ticker' has a description ('Ticker symbol (e.g. AAPL)'). The tool description adds no additional meaning or format details beyond the schema, so the baseline score of 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 clearly states that the tool performs a 'quick identity check' on a ticker, returning name, sector, industry, exchange, and asset type. This is a specific verb+resource pairing. However, it does not explicitly distinguish from sibling tools like get_instrument_overview, instead only implying a 'quick' and shallow scope.

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 phrase 'Useful before going deeper' gives clear context for when to use this tool: as a preliminary lightweight lookup before more detailed analysis. It does not explicitly name alternatives or exclusion criteria, but the guidance is unambiguous and practical.

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