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

No annotations are provided, so the description carries the behavioral burden. It discloses filtering behavior, default sorting, and that the tool is free, which is helpful. However, it does not mention whether the operation is read-only, what the response contains, or any pagination or access limitations.

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 compact and front-loaded: it states the object in the first sentence, then concisely lists filters and sorting behavior. The final 'Free' and demand-side framing add useful context without waste. Every sentence contributes.

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?

Given nine parameters, no annotations, and no output schema, the description provides a reasonable orientation but leaves gaps: it does not explain the required slug paramater, pagination behavior, or expected return shape. It is adequate for a simple filtered list, but not fully complete for an unannotated 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?

With schema description coverage at only 33%, the description compensates meaningfully by explaining is_provider, in_network, band, min_score, and sort defaults. It clarifies that score is the default sort and that is_provider=true targets API providers, adding value the schema alone does not fully provide. Required slug and page remain undocumented, but the description still covers most functional paramaters.

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 identifies the resource as a VC firm's portfolio companies and explains the core purpose: listing and filtering companies that are matched to the network and rated. It adds useful conceptual framing with 'the demand-side view of who a fund has backed,' which differentiates it from sibling tools like get_vc or find_vcs, though it does not name them explicitly.

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?

It implies usage by describing the demand-side portfolio view and available filters, but it never states when to choose this tool over alternatives such as get_vc, find_vcs, or compare_providers. There is clear context, but no explicit when-to-use or when-not-to-use guidance.

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