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

Annotations already declare readOnly=true, destructive=false, and openWorld=true (external network call), so the safety profile is covered. The description adds genuinely new behavioral context: it identifies SEC EDGAR as the upstream source (a public, rate-limited, external registry) and enumerates what comes back, which matters since there is no output schema. It stops short of noting failure modes for invalid or non-US tickers.

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?

A single sentence with zero filler: verb first, source second, return fields last. The colon-delimited field list is compact and front-loaded. Nothing could be removed without losing 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 one parameter at full schema coverage and no output schema, the description compensates well by enumerating the returned identity fields and naming the data source. What remains unaddressed is how this differs from the profile/ticker-search siblings and what happens on a miss (e.g., non-US or unlisted ticker).

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 single ticker parameter is fully documented with an example (AAPL), so the schema does the heavy lifting. The description adds only the constraint that the ticker must belong to a US public company. 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 verb ('look up'), a bounded resource ('a US public company's identity'), the data source (SEC EDGAR), and the exact fields returned (CIK, legal name, exchange, SIC, state of incorporation, fiscal year end). This makes the tool's scope immediately legible. It does not, however, distinguish itself from siblings like get_company_profile or get_ticker_search, which plausibly overlap.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative, despite a crowded sibling set that includes get_company_profile, get_ticker_search, and get_company_facts. The agent must infer that this is the identity-resolution entry point. Usage is implied only by the phrase 'identity'.

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