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

With no annotations, the description carries the full burden. It only says 'access detailed information' without disclosing what the output contains, whether it's historical or recent offerings, or any limitations. The second sentence is promotional rather than behavioral.

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 short, but the second sentence 'Track offering activity and identify potential investment opportunities' does not help an agent invoke the tool. It is not egregious, but it fails to earn its place by adding operational value.

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?

This is a simple one-parameter tool without an output schema. The description gives a minimal purpose but doesn't explain the return format or what 'equity offerings' encompasses. It's adequate for a basic getter but lacks sufficient context for an agent to know what to expect from the response.

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 fully documents the single 'cik' parameter with a description, so baseline is 3. The description adds no extra parameter semantics such as format or examples, but schema coverage is 100%, so the minimum viable score 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?

The description clearly states it 'Access[es] detailed information on equity offerings announced by specific companies' with a specific API reference. It identifies the tool's purpose and resource, but doesn't explicitly contrast with siblings like searchEquityOfferings or getLatestEquityOfferings, relying on the name for that distinction.

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?

No guidance is provided on when to use this tool versus alternatives. The description says 'specific companies' but doesn't mention prerequisites or exclusions, nor does it reference sibling tools for comparison.

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