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

Annotations already declare readOnlyHint/idempotentHint and no destruction, so the description does not need to restate safety. It adds value beyond them by naming the upstream source (api.adviserinfo.sec.gov), confirming no API key is needed, and enumerating the returned fields (CRD, employer, registration states, exam history). It does not disclose what happens when 'name' is left null or whether result sets are capped/paginated, which is the remaining gap.

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?

Front-loaded purpose sentence, then a scannable when-to-use list, then sibling routing, then provenance. Each block earns its place, though the bullets partially restate the opening sentence and could be tightened.

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 an output schema and full annotations present, the description need not explain return values or safety, and it correctly focuses on routing, source/auth context, and result content. It is nearly complete; only the optional-name behavior and result-set sizing are unaddressed.

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?

Reported schema description coverage is 0% at the top level, so the description must carry weight; it does establish that name-based lookup is the primary axis and lists the output fields available. However, it never mentions state filtering, row limits, or the cache-passing/resource-id pattern that the nested schema exposes, so an agent reading only the description would miss meaningful invocation options.

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 SEC IAPD ... for individual investment advisor representatives') and immediately scopes it to individuals rather than firms. The title, description, and named siblings (SearchIAPDFirm, SearchBrokerCheck) make the object of the search unambiguous.

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?

Provides an explicit 'Use this tool when' list covering the three canonical intents (individual lookup, IA registration verification, due diligence) and explicitly routes firm lookups and broker/dealer individuals to named alternative tools. Nothing is left to inference about when not to use it.

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