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

No annotations are provided, so the description carries the burden. It does well on output shape by enumerating the returned fields and noting the source (SEC), which signals a read-only lookup, but it never states that explicitly nor mentions data freshness, coverage of non-US listings, or what happens for an unknown ticker.

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?

Two sentences, front-loaded with the core identification and then a compact enumerated payload list. No filler; the only slight issue is that the long field enumeration delays the usage sentence to the end.

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 one-parameter read-only lookup with an output schema present, the description is nearly sufficient — it covers what the tool is, what it returns, and the audience. The remaining gap is input format guidance for the ticker, which the 0% schema coverage leaves unaddressed anywhere.

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 0% for the single required parameter 'ticker', so the description should compensate with format guidance (exchange-qualified symbol? case sensitivity? ticker vs CIK?). It only implies a US listing, leaving format ambiguous; the parameter concept is nevertheless self-evident from the name, so this is adequate rather than broken.

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: 'SEC profile of a US-listed company', then enumerates exactly which fields are returned (SIC, incorporation state, filer category, 10-K/10-Q links). The field inventory implicitly separates it from us_company_fundamentals and us_company_filings, though no sibling is named explicitly.

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?

'Use for due diligence and company research' gives a usage context but no exclusions or alternatives. Nothing tells the agent to prefer us_company_search when it has a name rather than a ticker, or us_company_fundamentals when it needs financials — usage must be inferred from the field list.

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