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

With no annotations, the description carries the full burden of behavioral disclosure, and it discloses almost nothing. It never states that this is a read-only lookup, what source it draws from, the granularity of the history (quarterly, annual, point-in-time), or what the return looks like. Only the word 'history' hints at temporal scope.

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?

It is a single short noun phrase with no filler, but it is a fragment rather than a front-loaded structured statement of purpose. Brevity here reflects under-specification as much as conciseness.

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 simple one-parameter lookup with no output schema, an agent still needs to know the data source, the reporting frequency, and whether a time series or a current value is returned. None of that is present, leaving real gaps for correct invocation and result interpretation.

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 parameter (ticker) is documented as accepting a ticker or CIK, so the schema does the work. The description adds no additional meaning about the parameter, which matches the baseline of 3 when coverage is high.

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 names the resource (shares outstanding and public float) but supplies no verb, so it reads as a label rather than a stated action. An agent can infer it retrieves data, and it is distinguishable from siblings like equity_dilution or company_facts, but the purpose is only implied.

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 indication of when to use this tool versus alternatives such as company_facts, equity_dilution, or financial_statements. No prerequisites, exclusions, or selection conditions are given.

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