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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that data is a 'free/teaser' view and that limited partners and peers are only 'previews', which tells the agent results are partial. It does not disclose whether one of id/url is mandatory in practice or any rate/auth constraints, so it exceeds the annotation bar only modestly.

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?

A single front-loaded sentence that lists the resource and its contents with zero filler. Nothing is repeated from the structured fields and no sentence is wasted.

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?

An output schema exists, so return-value detail is not required, and the description still summarizes what the profile contains. For a two-param read tool with annotations covering safety, this is essentially complete; only the routing guidance to sibling tools is absent.

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 both id and url are already documented with format examples and the 'pass exactly one of id or url' exclusivity rule. The description adds nothing about parameter format, so the baseline 3 is appropriate.

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 names the specific resource (PitchBook fund profile) and enumerates the fields it returns (strategy, status, manager, size, vintage), so an agent knows exactly what this fetches. It does not explicitly name sibling tools like pitchbook_company or pitchbook_investor, but the resource word 'fund' distinguishes it well enough among the pitchbook_* family.

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 explicit when-to-use guidance and no mention of alternatives such as the PitchBook search/facets tools or sibling profile tools. The phrase 'free/teaser' hints at a data-scope limitation an agent should consider, but it never states the condition or routing for selecting this tool.

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