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

Goes well beyond the readOnly/destructive/openWorld annotations by disclosing provenance behavior (prefers IR consensus, falls back to compiled, and states which kind answered each time), that coverage varies by issuer, that output carries units/accounting basis/statistical labels, and that it reads stored verified data and never scrapes on demand.

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?

Four sentences, each earning its place, with the core read purpose front-loaded and provenance/return caveats following. Slightly dense but no filler or repetition.

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 helpfully characterizes the return shape (units, accounting basis, mean/median/range/count labels, snapshot history, publication dates) and the coverage caveat. Only the absence of alternative-tool guidance keeps it from full completeness.

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%, so the schema already documents all nine parameters, including asOf, snapshotId, and the snapshot/metric/period/dimension labels. The description adds no syntax or defaults beyond that, so the baseline 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?

States a specific verb ('Read') and resource ('analyst consensus forecasts for a company') with the exact metric families covered (revenue, EPS, product, segment, operating). This clearly distinguishes it from estimation-adjacent siblings like GetGuidance, GetValuationMultiples, and GetCompanyKpis.

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 explains the internal preference logic (IR-published consensus over a compiled fallback), which implies when it's useful, but it gives no explicit when-to-use/when-not or comparison against competing siblings such as GetGuidance or GetFinancialFact. Usage is implied rather than routed.

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