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

No annotations are provided, so the description carries the full behavioral burden. 'Retrieve' implies a read-only, non-mutating lookup, which is useful, but it says nothing about behavior when the email matches no client, permission/auth requirements, or what 'detailed' entails. Adequate but with clear gaps for a no-annotation tool.

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; the resource and the lookup key come before anything else.

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 one-parameter read tool with a fully described schema this is close to sufficient, but with no annotations and no output schema the agent learns nothing about the returned record's structure or the not-found case. Minor, but a real 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 100% and the single parameter is fully documented in the schema ('Client email address'). The description only restates 'by email' and adds no format, case-sensitivity, or exact-match guidance beyond the schema.

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?

Specific verb ('Retrieve') plus specific resource ('detailed Client 360 CRM record for an individual client'), and the 'by email' qualifier makes it distinguishable from brightcanoe_search_clients. It stops short of a 5 because it never names the sibling or states the lookup-vs-search boundary 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?

The phrase 'for an individual client by email' implies the use case (single-record lookup when you already have the email) rather than a broad search, but there is no explicit when-to-use, when-not-to-use, or named alternative such as brightcanoe_search_clients.

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