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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond that: feeders and quarantined readings are excluded from GAV, the tape starts in 2011 with a partial current year, output is explicitly non-predictive, and the free-tier withholding rules (first 5 rows, count-only, contact values never returned, entitlement/locked reporting) are spelled out.

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?

It is dense and front-loads the series enumeration before the access caveats, so an agent gets the core purpose immediately. The entitlement/plan promotion at the end is somewhat long but is materially relevant to what data comes back.

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?

With no output schema and only 3 params, the description carries the return-shape burden well by explaining exclusions, date coverage, and locked/entitlement behavior. It does not explain the row/count semantics of limit or ordering of top_managers, a minor gap.

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 coverage is only 33%, but the description compensates by describing each view value in prose that maps to the enum (vehicles_by_year, managers_by_year, gav_by_year, vintages_by_year, drops_by_year, top_managers), and min_gav_usd is documented in the schema. The limit parameter (1-60) is not explained, keeping it short of a 5.

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 names a specific resource (derived real estate fund series by year) and enumerates the exact series produced: vehicles by year, first-time managers, GAV by year, vintages, drops, and top managers. This is clearly distinct from sibling record tools like get_re_fund_manager or get_re_fund_vehicle.

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 the tool is for aggregate/trend views rather than individual records, and the enumerated series make that use case inferable. However, it never states when to pick this over get_re_fund_manager, search_re_fund_vehicles, or the other RE fund siblings, and gives no explicit exclusions or prerequisites for selection.

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