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 does disclose the response contents (partners, active funds, website, portfolio focus), which is genuinely useful absent an output schema, and 'verified' hints at data trust. But it omits behavior on a missing/ambiguous slug, auth requirements, and rate limits.

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 well-formed sentence that front-loads the verb and resource before listing the payload. No wasted clauses, though it is a lightly padded enumeration of contents that could be tightened.

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 low-complexity, single-parameter lookup with no output schema, the description covers what the tool does and what it returns, compensating for the missing return schema. The main gap is routing guidance relative to search_investors and the thesis sibling, which keeps it short of 5.

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 description coverage is 100% and the single parameter already documents accepted forms with concrete slug examples. The description only restates 'a specific venture capital firm' and adds no syntax or format meaning beyond the schema, so the 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 ('Retrieves') and resource ('complete verified profile for a specific venture capital firm') and enumerates what the profile contains. An agent can tell it returns a single firm's record rather than a list. However, it never names or contrasts with siblings like search_investors or get_mode_vc_thesis_and_criteria, so the boundary is left implicit.

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 phrase 'for a specific venture capital firm' implies the caller must already know which firm, contrasting implicitly with search_investors, but this is never made explicit. There is no statement of when to use this versus the thesis or search tools, nor any prerequisite guidance beyond the required identifier.

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