datasets_pitchbook_limited_partners_item

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

No annotations are provided, so the description carries the full burden. It mentions the record is 'crawled', which hints at data provenance, but does not describe return format, error behavior, or any limitations. Being a read operation is obvious from 'Get', but no additional behavioral insight is offered.

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?

Two sentences, concise and front-loaded with the core action. The duplication between 'from dataset' and 'dataset id enum value' is slightly redundant but does not waste significant space.

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?

For a simple item fetch tool, the description is adequate: it specifies the input and that it returns one record. However, with no output schema, it does not describe the record's structure or fields, and no information is given about edge cases like missing ids, which is a moderate gap for a data retrieval 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 has 100% coverage with a clear description and example for the `id` parameter. The description adds little beyond restating that retrieval is by id, but the schema already fully documents the parameter, so the baseline score 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?

The description clearly states it retrieves a single PitchBook limited partner record by id from a dataset, using a specific verb and resource. It distinguishes itself from search/facets siblings by emphasizing 'by id', though a sibling `pitchbook_limited_partner` exists without the datasets prefix which could cause slight ambiguity.

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?

Usage is implied: you need an id to fetch a record. However, no explicit guidance is given on when to use this tool versus the search or facets alternatives, nor any mention of prerequisites like having the dataset id enum value.

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