datasets_pitchbook_investors_search

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

No annotations exist, so the description carries the burden. It adds context about the data source (crawled public profiles, discovered from PitchBook's public sitemap) and that it is stored in a search index. However, it does not disclose pagination behavior, result format, or staleness implications beyond the crawl mention.

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 concise, with three sentences that each add value: purpose, data source context, and sort options. It is front-loaded and contains no fluff or redundant 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?

Given 11 parameters and no output schema, the description provides enough context about what the tool searches and the data source. However, it does not describe return values or pagination limits beyond what the schema already contains. It is minimally sufficient but lacks rich behavioral context.

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. The description repeats the sort enum but does not add meaning beyond what the schema already provides. The schema descriptions are self-explanatory for all 11 parameters.

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 the tool searches the PitchBook investors dataset, specifies the resource (investor profile catalog) and action (search). It distinguishes from siblings like datasets_pitchbook_investors_item and pitchbook_investor by emphasizing it searches a dataset, not a specific item.

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 explicit guidance on when to use this tool versus alternatives. It does not mention when to prefer facets, item, or singular lookup tools. The usage is implied by the name and description but no exclusions or alternatives are provided.

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