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

With no annotations, the description carries the burden and it does disclose useful behavior: the summary returns totals, band distribution, and average rating, while view=full inlines the entire portfolio. It does not mention pagination, response size, or side effects, but this is clearly a retrieval tool and the main behavioral variation is documented.

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 short and front-loaded with the core purpose. The 'UNDERSTANDING' prefix and trailing 'Understanding plan' are somewhat redundant and add little, but they do not seriously hurt readability or scanability.

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 relatively simple getter with one required parameter, the description explains the main return contents and the view switch. There is no output schema, so slightly more detail about the full-portfolio response or volume could help, but the description is adequate for an agent to call the tool with reasonable confidence.

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 schema already describes view and context, giving 67% coverage. The description adds some meaning by explaining the effect of view=full, but it does not clarify the required slug parameter, which is undocumented in both the schema and the description. This leaves a notable gap for the only required parameter.

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 a specific verb and resource: retrieving one VC firm with identity, fund facts, and a portfolio summary. It also scopes the behavior by naming what the summary includes and by distinguishing the full view from the summary view, which helps separate it from broader search tools like find_vcs.

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: use this tool to get a single VC firm's identity, fund facts, and portfolio summary. However, the description does not explicitly say when to prefer get_vc over related alternatives like get_api/get_provider or vc_portfolio, nor does it state any exclusions.

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