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

Annotations cover read-only/open-world, but the description adds genuinely useful non-schema context: the per-call cost (0.001 credits) and the unauthenticated rate limit (25 calls/day per address). It does not, however, describe what the 'overview' payload contains or any pagination/format 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?

A single compact parenthetical delivers endpoint, cost, and auth limit with no wasted words, and the resource name is front-loaded. It is dense and efficient.

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 tool with no output schema, the description covers operational essentials (cost, auth) but never says what the overview returns or how it differs from sibling data tools. An agent can call it but cannot confidently judge its output.

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 0% for the single required parameter, so the description must compensate. Showing '{ticker}' in the URL path does imply the parameter is a stock ticker symbol, which adds some meaning, but there is no detail on format, case sensitivity, or exchange qualification.

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 essentially restates the name/title 'Company overview' with no verb, so the purpose is implied rather than stated. The endpoint URL hints at the resource ('companies/{ticker}/overview'), but it gives no differentiation from siblings like fundamentals, filings, or intrinsic_value, which all return company-level data.

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 guidance on when to use this tool versus alternatives such as fundamentals or intrinsic_value. The only context is operational (cost and credential limits), not selection guidance.

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