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

Annotations only provide readOnlyHint=true. The description adds substantial behavioral context: fields are sourced from specific filing types, the SIC scheme is intentionally labelled as coarser than GICS, and unestablished fields are surfaced in `gaps` rather than omitted. This meaningfully prepares the agent for data provenance and missing-value behavior.

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 description is front-loaded with the field list and then adds purposeful context about data provenance and `gaps` handling. It is longer than minimal, but each sentence contributes operational knowledge rather than redundancy.

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 read-only tool with a single parameter and an output schema, the description covers purpose, sourcing, and missing-value behavior well. The notable gap is the complete absence of guidance on how to format or resolve the `entity` parameter, leaving correct invocation partially to guesswork.

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?

The input schema has one required string parameter, `entity`, with no description and 0% schema coverage. The tool description never explains what `entity` should contain, such as a ticker, company name, or identifier, so it adds no value beyond the parameter name itself.

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 opening line identifies the tool as a company reference and enumerates concrete fields returned: description, employees, headquarters, CEO, sector, industry, and exchange. This clearly differentiates it from analytics-oriented siblings like get_company_brief or get_fundamentals, though no explicit verb such as 'returns' is used.

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?

The description implies the tool is for static company reference data sourced from SEC filings, with caveats about SIC versus GICS. However, it never explicitly states when to prefer this tool over siblings like get_overview or get_company_brief, nor does it provide exclusion conditions.

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