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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds real behavioral value by warning that 'exempt reporting advisers do not report these Item 5 figures', telling the agent to expect missing/empty AUM, headcount and fee fields rather than treating them as an error.

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?

Two sentences, zero padding: the first front-loads the operation and the full return surface, the second handles the alternative-tool routing. Every clause earns its place, especially the field list, which substitutes for the absent output schema.

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 enumerated field list and the exempt-reporting-adviser caveat give the agent a solid picture of what comes back. It stops short of covering failure modes (invalid/unknown CRD) or whether historical filings are included, which keeps it from a 5.

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%, so the crd parameter is already documented in the schema (integer, with example 231). The description confirms the entity scope (SEC-registered or exempt reporting adviser) but adds no format, validation or error semantics beyond the schema. 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?

States a specific verb (Get) and resource (full Form ADV profile for one SEC-registered or exempt reporting investment adviser) keyed by Organization CRD number, and enumerates the returned fields. It is clearly distinguishable from the sibling SearchInvestmentAdvisers, which it explicitly names.

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 closing line 'Find CRD numbers with SearchInvestmentAdvisers' routes the agent to the correct alternative when the required identifier is unknown, which is the key usage decision for a single-entity lookup. There is no explicit when-not guidance (e.g., what to do for a not-found CRD), but the context is clear.

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