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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context such as the 4-month lookback window and that price targets are measured against the current price, but it does not disclose other behavioral details like data freshness or market coverage limitations.

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 entire description is one well-structured, front-loaded sentence that uses a colon to efficiently list all returned components. There is no filler or redundant restatement of the tool name or annotations.

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 single-parameter read-only tool with no output schema, the description covers the main return dimensions well: rating, analyst count, price targets, implied upside/downside, and rating breakdown over time. It does not explicitly describe response formatting or currency, but these are not essential for an agent to decide to call 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?

Schema description coverage is 100% for the single 'symbol' parameter with the example 'SOFI', so the schema already carries the semantic weight. The description reinforces that the tool targets US stocks but does not add new parameter-level meaning 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 names the exact resource: Wall Street analyst consensus for a US stock, and enumerates the specific data returned (rating, price targets, breakdown). This clearly distinguishes it from siblings like get_superinvestor_consensus or get_stock_quote by specifying 'Wall Street analyst' and the forecast-oriented contents.

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 when to use it: when the agent needs analyst consensus data for a US stock. However, it provides no explicit guidance about when not to use it or which sibling tools might be better for related needs, such as current price or earnings data.

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