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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the module composition (profile + quote modules) and enumerates returned data types, which is useful, but discloses nothing about rate limits, auth needs, or whether symbols are validated.

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 tightly written sentences with the fetch action front-loaded, followed by contents and the routing hint. No filler, though the contents listing is somewhat thin on its own.

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 re-explained; the description still names the key data categories, and the routing hint covers the main selection risk. Adequate for a single-parameter info tool, with only the omission of symbol-format edge cases keeping it from a 5.

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?

With a single parameter and 100% schema description coverage, the schema already documents 'symbol' with an example (AAPL). The description adds no format or exchange-suffix guidance (e.g. 'AAPL' vs '7203.T'), so baseline 3 is correct.

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 uses a specific verb+resource ('Fetch a Yahoo Finance profile and quote modules for a ticker symbol') and characterizes the payload as a broad security overview. It distinguishes itself from ticker_history, but does not differentiate against other siblings like yahoo_finance_ticker_quote or yahoo_finance_ticker_financials, which overlap with the 'quote' and 'statistics' modules it mentions.

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?

Gives clear selection guidance: 'use this for a broad security overview rather than historical prices,' which explicitly routes the agent away from yahoo_finance_ticker_history. It offers no other alternatives (e.g. ticker_quote for a live quote, ticker_financials for statements), so it stops short of full when/when-not coverage.

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