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

Annotations confirm a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description goes well beyond that: it warns values are not restated, that vantage_date only bounds visible filings rather than restating figures, and that get_financials/get_metric_history flag a LOOK-AHEAD. That is genuine behavioral context an agent cannot derive from structured fields.

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-loaded with purpose then contents then routing, and each sentence carries routing or scope information. The final paragraph on non-point-in-time semantics is dense and long, but it is load-bearing rather than filler.

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?

No output schema exists, yet the description enumerates the returned sections thoroughly enough that an agent knows what to expect, and it covers freshness semantics, depth presets via the schema, and sibling boundaries. Nothing needed to call it correctly is missing.

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%, and the depth enum (snapshot/core/full with character budgets) is fully documented in the schema itself. The description adds only the 'latest snapshot only' framing, so the baseline 3 for a schema that does the heavy lifting 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?

States a specific verb (get), resource (company overview), and scope (comprehensive, single call) then enumerates the exact data families returned: valuation, profitability, cash flow, balance sheet, capital allocation, segment/geographic mix, earnings insights and flags. It actively distinguishes itself from siblings such as get_financials, get_xbrl_facts, get_filing_index and compare_companies.

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?

Explicit routing: 'Latest snapshot only — use get_financials for multi-year trends, get_xbrl_facts for multi-period segment history, get_filing_index for a signal map...'. It also states the negative case (not point-in-time) and names the exact alternative tool family for 'as of <past date>' work, including the vantage_date parameter.

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