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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so safety is covered. The description adds real value beyond them: data provenance (Form D filings) and the freshness angle (deals appear before public announcement), which tells the agent what kind of information it is getting.

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?

Two tight sentences with the core resource and source front-loaded before the usage clause. Every phrase carries weight, though the quoted use-case list is slightly padded.

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 3-param, no-output-schema read tool with rich annotations, the description supplies the data source, the returned fields, and the intended workflow. It does not describe result ordering or pagination behavior, but the essential call context is present.

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%, so limit, min_amount, and company_name are already documented, making 3 the baseline. The description loosely maps the output fields (fund name, target or raised amount) to those parameters but adds no syntax or filtering nuance beyond the schema.

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 a specific resource (new investment funds raising capital), the data source (SEC Form D filings), and the fields surfaced (fund name, target/raised amount, the filing). An agent can distinguish this from search_funding_rounds and search_investors because it explicitly scopes to fund vehicles rather than company rounds or investor entities.

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?

Gives concrete use cases ("who is raising a fund", LP and allocator work, catching a new vehicle before announcement), which clearly signals when to reach for it. It stops short of naming an alternative sibling or a when-not condition, so it is strong context without explicit routing.

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