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

Goes well beyond the readOnly/idempotent annotations: it discloses the entitlement model (first 5 rows plus counts when unentitled, only first 3 related names per section, contact values never returned), that anomalies are leads not conclusions with data-quality rows separated, and that book size/revenue are marked UNKNOWN and never estimated. These are exactly the behavioral traits an agent needs before relying on results.

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 content is front-loaded but delivered as one enormous sentence with nested parenthetical inventories, and much of it is an item-by-item catalogue rather than decision-relevant guidance. It is information-dense yet hard to scan, so it is only moderately well structured.

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, the description carries return-value disclosure and does so thoroughly: section-by-section contents, the entitlement/locked reporting contract, and the UNKNOWN policy. For a single-parameter read tool with annotations covering safety, nothing an agent needs to call and interpret it is missing.

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% for the single dfx_id parameter, and the schema already documents the dfx:ria:<uuid> or CRD forms. The description repeats the accepted identifier types without adding format, validation or fallback semantics, so the baseline 3 applies.

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 specific resource and enumerates its contents precisely (Form ADV fields, derived metrics, archetypes, anomalies, retention, contact path) and names the accepted identifiers. It is clear what the tool returns for one practice, but it never distinguishes itself from close siblings like get_ria_firm, get_ria_advisor or search_ria_practices, leaving the agent to infer the boundary.

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 only implied by the content inventory and the note that it accepts a dfx:ria: id or CRD; there is no explicit 'use this when you need X, use Y otherwise' guidance and no alternatives named. The access-tier paragraph explains what happens on a free plan, which is helpful context, but it is not selection guidance.

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