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

With only readOnlyHint=true available, the description carries the rest and does so well: null + is_absence=true rows are legitimate answers, metric_availability explains why, values are confidence-gated, and needs_review rows are excluded. It also discloses extraction lineage (SEC exhibits, Oxford Ledge parse) and that reads are free.

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 scope, then the absence semantics, then filters and the sibling alternative. Dense but every clause earns its place; the all-caps emphasis is slightly noisy but not wasteful.

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 explains what rows look like (value/is_absence/metric_availability), what is filtered out, and where data comes from. For a read-only panel tool this covers everything an agent needs to call and interpret it correctly.

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 coverage is 100%, so the schema already documents ticker, limit, metric, period, and industry. The description names the same three optional filters and adds the useful constraint that there is no cross-issuer read, but supplies no extra syntax or format detail beyond the schema. 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?

States a specific resource and scope ('Tier-3 KPI PANEL for ONE issuer'), enumerates the metric dimensions (ARR, RPO/cRPO, NRR, etc.), and names the sibling it is NOT (ol_operating_kpis) plus the source. An agent can distinguish it from every sibling without opening a schema.

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?

Explicitly says per-issuer by design and routes broad cross-industry KPI queries to ol_operating_kpis. The 'ABSENCE IS FIRST-CLASS' note tells the agent how to interpret null rows rather than retry or substitute. When-to-use and the alternative are both stated.

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