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 adds a genuinely useful behavioral trait beyond annotations: the data is a 'free/teaser overview' with only 'previews' of associated entities, warning the agent that results may be truncated. It does not cover auth requirements, rate limits, or whether the teaser differs from a paid profile.

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 dense sentence that front-loads the resource name and then lists the payload. Every clause carries information, though the enumerated lists make it slightly dense to parse. No wasted sentences.

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 values need not be explained and the description correctly does not dwell on them. However, for a tool sitting among many PitchBook entity tools, the absence of any routing guidance leaves a gap in selecting it correctly over pitchbook_company or pitchbook_investor.

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%, and both parameters (id and url) are fully documented with the 'pass exactly one of id or url' constraint and an example id format. The description adds nothing beyond the schema, 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?

The description names the specific resource (PitchBook advisor / service provider profile) and enumerates what it returns: a teaser overview, contact/HQ, and previews of serviced companies, deals, co-lenders, and subsidiaries. The parenthetical '(service provider)' distinguishes it from the sibling pitchbook_company, pitchbook_investor, pitchbook_fund, and pitchbook_limited_partner tools. The verb is implicit (profile lookup) rather than stated, keeping it just short of a 5.

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 when-to-use guidance, no mention of when to prefer this over the sibling entity-lookup tools, and no note that it is a preview rather than a full data pull. The agent is left to infer usage entirely from the resource name.

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