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

Annotations already declare this as read-only, idempotent, and non-destructive. The description adds the output fields (consensus, price target, upside), which gives some behavioral context beyond the annotations. However, it does not discuss error handling, rate limits, or other behavioral nuances, so it remains at a moderate level.

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 very concise: one sentence stating purpose, followed by a clear Args section. It is front-loaded with the key information and contains no filler. Every sentence earns its place.

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 with no output schema, the description adequately covers the main purpose and expected return fields. It does not explicitly mention that only one ETF is processed at a time or define terms like 'upside', but the core information is sufficient for an agent to invoke the tool correctly.

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?

The input schema only defines 'ticker' as a string with no description. The tool description compensates fully by explaining what ticker means and providing an example ('QQQ'). This is clear and directly aids the agent in selecting and formatting the parameter.

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 returns the analyst forecast for a specific ETF, listing consensus, price target, and upside. It uses a specific verb ('Returns') and resource ('analyst forecast for a specific ETF'), distinguishing it from sibling tools like get_etf_exposures or get_etf_screener.

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 implies the tool is for retrieving forecast data for a single ETF, which narrows its scope. However, it does not explicitly mention when to prefer this over related tools like get_etf_analysis or get_etf_holdings, nor does it provide exclusions. Usage context is present but not fully articulated.

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