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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the trailing 'Read-only.' is redundant. The one genuinely useful addition is that each investment carries 'the evidence it rests on', hinting at enriched/provenance-laden output, but the description says nothing about aggregation depth, size of the response, or whether membership is direct vs transitive.

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 tight sentence with no padding, and the core noun ('One company or VC firm') is front-loaded. It reads as a content inventory rather than a functional statement, which slightly hurts scanability, but nothing is wasted.

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?

An output schema exists, so return-value detail is not required, and the safety profile is covered by annotations. However, for a graph-entity tool taking two IDs, the description leaves open what the second ID scopes and whether people/portfolio lists are complete or truncated, which an agent needs to interpret the result.

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% but the schema only labels both parameters as 'UUID value wrapper'. The description gives no hint why both companyId and organizationId are required (tenant scoping vs the entity itself), which is the one thing an agent could get wrong here. Baseline 3 applies since the schema documents the fields, but no value is added.

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 characterizes the entity returned (one company/VC firm with its founders, partners, employees, investments received and portfolio built) but never states the operation directly or names the organization being fetched. It does not distinguish this from fundraising_list_network_organizations, fundraising_get_network_person, or fundraising_get_network_group, so an agent must infer the single-org, detail-returning nature.

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?

There is no statement of when to use this versus the closely named sibling list_network_organizations or get_network_person/get_network_group. No prerequisites, no exclusion conditions, only an implied 'use it when you want one org's details'.

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