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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description still adds substance by listing returned fields and explicitly noting that national IDs like SSN are never returned, plus what happens with zero filters. Pagination absence is implied but only fully stated in the limit param.

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?

Four tight sentences with the scope and return payload front-loaded. The trailing 'POST individuals/search' endpoint note is minor but not wasteful.

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?

No output schema exists, and the description compensates by enumerating returned fields and the SSN exclusion. The main residual gap for an 8-param search tool is match-mode behavior and ordering guarantees beyond updated_since.

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?

Adds real semantic value with 'filters combine' and the updated_since use case, but leaves the most important search semantics unexplained: whether first_name/last_name/email match exactly or partially. Schema coverage is 63%, and documented params (limit, phone, group_id, updated dates) already carry their own descriptions.

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 and resource ('Search individuals (clients and contacts) in AgencyBloc') and names the underlying endpoint. It is clearly distinguishable from siblings like get_individual (single record) and create_individual.

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?

Explains filter semantics ('all filters are optional and combine; with none you get the first records') and gives a concrete use case ('Use updated_since to find recently changed people'). It stops short of explicitly routing between this tool and get_individual or search_leads_by_phone.

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