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

Far beyond the readOnly/idempotent annotations, it discloses the entitlement model in detail (5-row lists with locked.count/by_type, records naming only subject plus 3 related names per section, contact values and decision-maker names never returned), the GAV definition and its exclusions, the quarantined-reading rule, and the 2011-onward tape with coverage_live. This is exactly the extra context annotations cannot carry.

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 first ~90 words are a single run-on sentence listing a dozen returned sections, so it is not front-loaded with purpose and is hard to scan. Most content does earn its place given the breadth of the payload and the access caveats, but the structure is weak rather than concise.

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 a single documented parameter, the description carries the full burden and does so: it describes every returned section, the identifier forms, data-coverage limits, and the entitlement/locked contract for every answer. An agent has everything needed to call and interpret it.

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 100% and the single dfx_id parameter is already documented as a dfx:ref uuid or CRD string, so the description's restatement ('Accepts a dfx:ref: id or the manager's CRD') adds nothing new. Baseline 3 applies when the schema does the heavy lifting.

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 name and title establish this as a single-resource fetch for one real estate fund manager, and the description enumerates exactly what comes back (card, ten largest vehicles, family by vintage, bindings, lenders, maturities, Schedule A people, cross-graph records). It is distinguishable from the sibling search_re_fund_managers by being 'one ... in full', though the description never states that contrast explicitly.

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?

Usage is implied rather than stated: the exhaustive content list implies 'call this when you have an identifier and want everything about one manager'. There is no explicit when-to-use/when-not, and no sibling (search_re_fund_managers, get_re_fund_vehicle, get_re_fund_trends) is named as an alternative. The coverage notes (2011 ADV tape, only a few hundred managers with passing bindings) do give useful interpretive context.

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