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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the bar is lower; the description still adds real context beyond them: data provenance ('every figure is the company's own, from SEC EDGAR'), a restatement rule and method versions, the ten-year cap, a schema identifier with dictionary path, and a non-advice disclaimer. It does not describe payload size, latency, or what happens for unmatched tickers/CIKs.

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?

The lead clause is well front-loaded, but the body is one long run-on that stacks identity fields, method/card contents and a financial line-item list into a single sentence, which is hard to scan. Nearly every clause carries information, but the density works against quick parsing.

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 full burden of explaining return values and does so thoroughly — covering identity fields, derived scores, peer context and per-row XBRL provenance with accession number and URL. Only minor gaps remain around output shape/pagination and edge cases for unresolvable companies.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents it fully. The description's 'name, ticker or CIK' merely restates the schema's own wording and adds no disambiguation guidance (e.g., ticker-vs-CIK precedence, case sensitivity, ambiguous names), making the baseline 3 correct.

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 states a specific verb+resource ('build a company profile') and enumerates the payload precisely (identity, Edgar/Edgarette card, up to ten fiscal years of financials), so an agent knows exactly what comes back. It never names a sibling tool it is distinct from, so it falls short of a 5.

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?

Usage is only implied — 'any SEC filer (name, ticker or CIK)' signals broad applicability and 'one document to build a company profile from' suggests it is the consolidation/starting call. There is no explicit when-to-use versus watch_company, get_company_performance, get_board_test or the other siblings, and no prerequisites or exclusions.

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