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

With no annotations and no output schema, the description carries the full behavioral burden, yet it only implies a time series via 'over time'. It says nothing about granularity (quarterly/annual), units, data source, or whether the ticker is required or optional — all things an agent would need for a single-param lookup tool.

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 tight sentence with no filler and the core content front-loaded. It is efficient, though arguably under-specified rather than genuinely concise given what it omits.

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 tool with no output schema, the description conveys the topical scope of the data, which is the minimum needed to route a query. However, the missing verb, return granularity, and distinction from shares_outstanding leave clear gaps.

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 coverage is 100% and the single parameter carries its own description ('ticker or CIK'), so the schema already does the work. The tool description adds no parameter meaning beyond that, which matches the baseline 3 for high-coverage single-param schemas.

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 data domain (share counts, dilution, stock comp, buybacks) but is a bare noun phrase with no verb, so it never says what the tool actually does with them (retrieve? compute? chart over a period?). It also does not differentiate itself from the close sibling shares_outstanding, which overlaps on the share-count dimension.

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 guidance, no prerequisites, and no mention of the alternatives (e.g. shares_outstanding for a point-in-time count vs. this tool for the trend). The agent must infer usage entirely from the topic phrase.

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