search_form_d_raises

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions the basic search action and does not disclose pagination behavior, output format, authentication requirements, or any restrictions, making it inadequate for safe usage.

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 single sentence is concise with no filler, but it is under-specified for a tool with six parameters. The brevity reflects a lack of essential information rather than efficient completeness, so it is more comparable to under-specification than to well-structured conciseness.

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?

The description is grossly inadequate given the tool's complexity. With no output schema, no annotations, and six parameters, it fails to explain return values, pagination, filter semantics, or use cases. The agent cannot correctly select or invoke this tool based on the description alone.

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 description does not explain any of the six parameters. Schema description coverage is only 33% (limit and cursor have descriptions), leaving q, state, industry, and min_amount undocumented in both the schema and the description. The description fails to compensate for the low coverage.

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 specifies the action 'search' and the resource 'Form D private-placement capital raises' with a specific filing type, distinguishing it from sibling search tools like search_filings or full_text_search.

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 such as search_filings or full_text_search. There is no mention of preferred use cases, exclusions, or complementary tools.

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