get_consensus_forecasts

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the key quirk that there is no server-side instrument filter, that the tool internally pages through the whole universe, and that it returns {"error": ...} when nothing matches. It also flags page_number as deprecated and ignored, which is exactly the kind of behavioral detail annotations cannot convey.

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?

Front-loads purpose, then the mechanism paragraph that justifies the unusual paging design, then a compact Args block. Every sentence adds information an agent needs; nothing is padding.

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?

With no output schema, the description still names the returned payload (target price, recommendation, analyst count) and the failure shape, and it explains pagination and the internal scan limit. Nothing material is missing for correct invocation or result interpretation.

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 0%, so the description carries the full burden and does: instrument_id accepts ticker/FIGI/ISIN/instrument UID/asset UID, page_limit defaults to 100 with non-positive meaning 100, max_pages defaults to 50 and must be at least 1, and page_number is a deprecated no-op. Every parameter's type and edge-case behavior is explained.

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?

States a specific verb and resource (analyst consensus forecast for one instrument) and enumerates the returned fields: target price, recommendation, analyst count. That is enough to distinguish it from generic sibling tools, though it never explicitly contrasts itself with the adjacent get_forecast_by, leaving some overlap 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?

Usage is implied rather than stated: supply an instrument identifier and receive the matching consensus item. There is no explicit when-to-use/when-not guidance and no pointer to get_forecast_by or the other forecast/instrument lookups as alternatives, so an agent must infer routing from the descriptions of the siblings.

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