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

No annotations are provided, so the description must carry the full behavioral burden. It does disclose the return payload's key fields (id, name, status, platform, currency, principal, entry fee, fee fractions, dates, target company) and enumerates the status enum values, which is helpful context. But it omits pagination behavior (default limit, max limit), ordering, and any auth or rate-limit details. For a list tool with no annotations, this is a moderate gap.

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 with zero waste. The first states purpose and scope; the second lists the return fields and then the follow-up tools. Front-loaded and earns every word.

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?

The description is largely complete for a list tool: it explains what the tool returns, clarifies the domain, and routes the agent to related tools. It does not mention pagination defaults or limits despite offset/limit parameters, and there is no output schema to fall back on, leaving a small gap. Overall, adequate but not exhaustive.

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%, so all four parameters (limit, offset, status, platformId) are documented in the schema. The description does not repeat parameter syntax or add format details, and it correctly relies on the schema for that. Baseline 3 is appropriate when schema coverage is complete.

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 ('List') and resource ('venture deals'), plus a parenthetical clarifying the domain (private/illiquid investments through SPVs, syndicates, or direct vehicles). This distinguishes it from siblings like list_venture_events, list_venture_platforms, and list_portfolio_transfers, which cover adjacent but different resources.

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?

Provides a clear follow-up path: 'Use the returned id with get_venture_deal, get_venture_deal_metrics, list_venture_events, and update_venture_deal.' This tells the agent what to do next with the results. However, it doesn't state when this tool should be preferred over alternatives (e.g., if there were a search variant) or any prerequisites, so it stops short of explicit when-not guidance.

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