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

Beyond the annotations (readOnly, idempotent), the description discloses important behavioral and data semantics: GAV is defined as assets on a filing date and excludes fund size/commitments/dry powder, quarantined readings are omitted, data only covers 2011–2024 so no 2025 facts exist, and holdings/properties/loans appear only when a binding passed blind labels. These are nontrivial caveats that help the agent interpret results and avoid mis-calling.

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 a dense single paragraph; the first sentence is a very long enumeration of contents separated by commas, which is hard to scan. Though every sentence carries relevant information (input format, GAV definition, temporal range, filtering), the structure could be improved with bullets or shorter sentences. It is not excessively long, but not well organized.

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 tool returning a large aggregate with no output schema, the description covers the input options, the major data components, key definitions, the data time range, and filtering constraints. It doesn't explicitly mention return format or error behavior, but given the annotations already establish safety and the description is detailed, it is largely complete for correct invocation.

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 dfx_id as 'A dfx:ref:<uuid> manager id, or the manager's CRD as a string' with 100% coverage. The description simply repeats this in prose ('Accepts a dfx:ref: id or the manager's CRD') without adding examples, value formats, or additional parameter nuances, so it stays at the baseline for full schema coverage.

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 states a clear, specific verb-and-resource: it returns the complete record for a real estate fund manager, enumerating the manager card, vehicles, family, bindings, properties, loans, events, Schedule A, and cross-graph records. The title 'One real estate fund manager in full' and the comprehensive enumeration distinguish it from siblings like get_re_fund_vehicle and search_re_fund_managers.

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 description implies usage via its comprehensive scope and the acceptances of dfx:ref id or CRD, and it adds temporal guidance ('sworn tape runs 2011 to 2024'). However, it does not explicitly name alternatives, state when not to use this tool, or contrast with search_re_fund_managers or get_re_fund_vehicle, leaving usage guidance partly implicit.

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