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

Extremely thorough beyond the lone readOnlyHint: it discloses the anonymous 3-row truncation and `partial`/`total_metrics` signalling, that values are AS-REPORTED and confidence-gated, and the ambiguous meaning of available=false (uncovered industry vs. empty issuer vs. outage) with a no-retry directive. Source (SEC 10-K/10-Q/8-K exhibits) and FREE status are also stated.

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 the purpose (operating KPIs for one issuer) before the qualification chain about deployment flags and coverage. It is dense and partly run-on with heavy parentheticals, but nearly every clause carries operational information.

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 carries the return-shape burden and does so by enumerating the panel fields (ticker, industry, metrics, available, partial, total_metrics, period, as_of, provenance, caveat). Coverage caveats, gating, and source are all present, so an agent has what it needs to call and interpret results.

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?

With one parameter and 100% schema description coverage, the schema already documents `ticker` as a mandatory single issuer symbol including the no-cross-issuer-screen note. The description largely repeats this ('ONE issuer', 'Per-issuer by design') rather than adding new syntax or format guidance.

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+resource with concrete examples (same-store sales, RevPAR, load factor, medical-loss ratio) and scopes it to ONE issuer extracted from SEC filings. However, it never acknowledges the very similar sibling `ol_issuer_kpi_panel`, leaving the agent to guess which panel tool to call.

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?

Gives explicit operating context: anonymous vs keyed callers, the 3-row anonymous cap, and a clear 'do not retry with variations' instruction for available=false. It also states the tool is per-issuer by design, ruling out cross-issuer screens, but names no alternative sibling to use instead.

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