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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: 'Get' implies a read, but there is no statement about permissions, whether the dossier is expensive/rate-limited, or what happens with a missing or unauthorized client_id. The output schema covers return values, but the operational profile is undocumented.

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 front-loaded sentence with no filler, and the content enumeration is efficient. It is appropriately sized for the amount of information conveyed, though it is arguably under-specified rather than tight.

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. However, with zero annotations, zero schema description coverage, and no usage guidance, the definition leaves the agent guessing about when this aggregate call is preferred over the narrower sibling getters.

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 0% and the description says nothing about either parameter. The required client_id is inferable from 'client dossier', but firm_id (with an empty-string default) is completely unexplained in both schema and description, leaving ambiguity about multi-firm scoping.

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?

States a specific verb (Get) and resource (client dossier), and enumerates the aggregated contents — profile, entities, AUM, review status, team assignments — which signals it is the composite view rather than a single-facet getter. It does not explicitly contrast itself with siblings like get_client_goals or get_client_team, so it falls short of a 5.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives despite several sibling tools (get_client_goals, get_client_team, get_client_reviews_due) that fetch subsets of the same data. The agent must infer that this is the aggregate call.

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