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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral context by naming the analytical categories (legal, tax, practical) and example fact patterns (settlor-as-beneficiary, lender consent, offshore, time pressure), which helps the agent anticipate what the call will compute. No contradiction with annotations.

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?

One sentence front-loads the core action and output scope, then adds a compact parenthetical of examples. There is no redundancy and every phrase contributes to understanding the tool.

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?

Given a rich nested input schema, an output schema, and strong read-only annotations, the description is enough for an agent to select and invoke the tool correctly. It does not cover workflow sequencing or alternatives, but those are not critical for this isolated retrieval-style tool.

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?

The input schema has 100% description coverage, with detailed per-field explanations and examples for every intake property. The description only adds the general notion of 'customer facts', which is already reflected in the schema's description. The schema carries the parameter-meaning burden, so the description adds marginal semantic value.

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?

The description states a specific verb and resource: 'Return legal, tax, and practical red flags'. It also specifies the input source ('detected from customer facts') and gives representative flag types, making the tool's purpose distinct from sibling list/retrieval tools.

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 description makes the trigger condition clear: use this tool when customer facts are available and risk flags need to be surfaced. It does not explicitly name alternatives or exclusion criteria, but no sibling tool overlaps with the red-flag function, so the context is sufficient.

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