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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description does add one genuinely useful behavioral note — the content is a 'free/teaser overview' with only 'previews' of investments/exits — which warns the agent that the payload may be truncated relative to a full PitchBook subscription.

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 compact clause front-loads the entity and lists the returned content without filler. It is dense but readable, 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 annotations cover the safety profile. The main remaining gap is the absence of any routing advice versus the search/dataset siblings, which matters in a catalog this large with many near-identical pitchbook entities.

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% and both parameters (id, url) are fully documented in the schema, including the mutual-exclusivity rule. The description adds nothing about the id format or the exactly-one-of constraint, so 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?

States a specific verb+resource ('PitchBook investor profile') and enumerates the content sections returned (overview, contact/HQ, investments, exits, co-investors). It implicitly distinguishes the investor entity from siblings like pitchbook_company and pitchbook_fund, but never explicitly names them, so it does not fully guide disambiguation.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as the datasets_pitchbook_investors_search tool or the dataset-backed pitchbook item tool. The agent must infer from the name that this is a by-id/url lookup rather than a search.

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