datasets_pitchbook_advisors_item

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

With no annotations provided, the description carries the full burden of disclosing behavior. It reveals that the tool performs a read operation ('Returns') and that the data is 'crawled' from a specific dataset, but it does not mention error behavior (e.g., what happens if the ID is not found), rate limits, or the completeness of the returned record. The description is not misleading but adds only basic behavioral context.

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 a single, focused sentence of 19 words. It front-loads the verb and resource and includes the necessary dataset enum value without any filler. Every word contributes to clarifying the tool's purpose.

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?

This is a simple, single-parameter tool with no output schema, so the description should clarify what the return value is. It says 'Returns one crawled PitchBook advisor record' but does not explain the structure or contents of that record. The dataset enum value is useful context, but the absence of output schema means more detail about the return value would improve completeness. Overall, it is minimally sufficient for a fetch-by-ID tool.

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?

The input schema already describes the `id` parameter fully with an example, giving 100% coverage. The description adds minimal extra meaning beyond 'by id', which is echoed in the schema. Since schema coverage is complete, a baseline of 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 uses the specific verb 'Get' and clearly states it returns one crawled PitchBook advisor record by id from dataset id enum value `pitchbook-advisors`. This distinguishes it from sibling tools like datasets_pitchbook_advisors_search or _facets, which are for searching or aggregating instead of fetching a single record by ID.

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?

The description implies usage when you have a specific PitchBook advisor ID by stating 'by id'. However, it does not explicitly mention alternatives or when not to use this tool, such as 'use datasets_pitchbook_advisors_search to find advisors without an ID'. The context is clear but not explicitly contrasted with siblings.

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