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

Beyond the readOnlyHint annotations, it explains the data source (public EDGAR), the semantics of a Form D (a notice filed after selling securities, not a funding announcement), that amounts are self-reported, and the exact failure string returned before Mode VC data loads. That is substantive behavioral context annotations cannot convey.

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?

Front-loaded with the core action and returned fields, then two short clarifier sentences about Form D semantics and the data-availability caveat. Slightly dense first sentence but every sentence carries information.

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, the description compensates by enumerating the returned fields (issuer, amount sold, related persons, EDGAR link) and flagging the self-reported nature of amounts plus the not-yet-loaded state. An agent has everything needed to call and interpret results.

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 all five filters (limit, query, state, industry_group, min_amount_sold) are already documented in the schema. The description adds no per-parameter syntax or defaults, so the baseline 3 applies.

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 verb and resource ('Lists recent SEC Form D filings') plus scope qualifiers (venture funds and technology companies, last few filing days, public EDGAR data). An agent can distinguish it from get_firm_filings and the calc_* siblings without opening any schema.

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?

It implies when the tool is appropriate (recent Form D activity) and gives a when-not caveat ('Returns

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