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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description goes well beyond that: it discloses that the tool prefers issuer-published consensus, falls back to compiled consensus, always states which kind answered, returns original units and accounting basis, exposes snapshot history and publication dates, and never scrapes on demand. This is rich behavioral context not present in the annotations.

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?

Five sentences, each earning its place: the first states purpose, the second explains sourcing behavior, the third summarizes return contents, the fourth is a caveat about coverage, and the fifth clarifies no on-demand scraping. The most important information is front-loaded.

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 tool with nine parameters and no output schema, the description carries the return-value burden well by naming units, accounting basis, label types, snapshot history, and publication dates. Combined with full schema descriptions for every parameter, an agent has enough to invoke the tool correctly and interpret the result.

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 defaults and semantics. The description adds useful contextual links such as snapshot history and publication dates, but it does not need to restate parameter meanings; baseline 3 is appropriate.

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 begins with a specific verb and resource: 'Read analyst consensus forecasts for a company', and elaborates on the kinds of metrics included (revenue, EPS, product, segment, operating). This clearly distinguishes it from generic quote or price tools and from related but different forecast tools.

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 intended use is clear: call this when you need analyst consensus estimates for a company. It also provides useful context such as sourcing preference, fallback behavior, and coverage variability. However, it does not explicitly name alternatives or state when not to use this tool versus a sibling like GetGuidance or GetCompanyKpis.

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