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

readOnlyHint and openWorldHint already declare the safety and openness profile. The description adds useful provenance context (crawled public catalog discovered from PitchBook's sitemap, only previews of LPs/peer funds), which warns the agent the data is a partial public snapshot, but says nothing about pagination limits or result freshness.

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?

One front-loaded sentence identifies the tool and its contents without redundant restatement. The nested parentheticals carry real information but make the sentence dense.

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 an output schema present and 100% schema coverage, the description only needs to convey data scope and provenance, which it does. It is adequate for a 9-param search tool, though noting the pagination cap behavior or data-freshness caveat would round it out.

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 every parameter (q, page, sort, run_id, page_size, fund_status, fund_strategy, vintage bounds) is already documented. The description contributes no additional parameter semantics, so the baseline of 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 clear verb (Search) and resource (PitchBook funds dataset), and enumerates the fields held (strategy, status, manager, size, vintage, LP/peer previews). It distinguishes the tool from datasets_pitchbook_funds_item and datasets_pitchbook_funds_facets by implication of 'search', though it never names those siblings explicitly.

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?

There is no statement of when to use this search vs the funds facets or item tools, and no exclusions or prerequisites. The agent must infer that this is the list/query entrypoint from the name alone.

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