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

Annotations only declare readOnlyHint=true, so the description must carry the rest — and it does add real substance: the no-default-minimum behavior and the meaning of a null offering_amount. These are non-obvious data traits an agent would otherwise misread as a zero-value raise. It stops short of describing return shape or ordering, but the safety profile is already covered.

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?

Three sentences, each load-bearing: the first establishes scope, the second the default/threshold behavior, the third the null-amount gotcha. The most decision-relevant constraint (no minimum applied) is front-loaded after the scope line.

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?

With no output schema and no required parameters, the description does the necessary work of flagging the null offering_amount semantic — the main trap for a consumer. It leaves minor gaps (result ordering, whether limit caps silently) but nothing that would cause a mis-call.

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%, so the baseline is 3, but the description adds meaning the schema lacks: min_amount defaults to no filter rather than some implicit threshold, and it explains the offering_amount null convention. This goes beyond restating schema text, though it doesn't quantify units or tie the null note directly to a named parameter.

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?

States the specific resource (SEC Form D private placements) and the filterable dimensions (issuer name, resolved ticker, date, minimum amount), which is enough to distinguish it from every sibling, none of which cover Form D raises. The retrieval verb is implied rather than stated, keeping it just below a 5.

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 clarifies the default filter posture ('No minimum size is applied: pass min_amount to impose one'), which is genuine usage guidance for this parameter. It does not, however, state when to reach for this tool versus adjacent datasets (e.g. insider_trades, institutional_holders), so the guidance is implied rather than explicit.

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