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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description still adds meaningful behavioral context beyond them: the brief is 'built from source fields, not generated guesses' and self-reports 'confidence and limitations', which tells the agent how much to trust the output. It omits latency/cost and whether the brief is cached or composed per call.

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 dense sentence that front-loads the deliverable and then enumerates its contents; no filler or marketing language. The enumeration is long but each item corresponds to an actual section of the returned brief, so it earns its space.

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 description must (and largely does) describe the return shape: sections, sources, confidence, and limitations. Combined with annotations covering the safety profile, an agent has enough to invoke it correctly. The remaining gap is routing guidance versus sibling tools, which is a usage concern rather than a return-value 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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema's terse 'Watchlist name or id.' by explaining the watchlist's effect on the output ('who may be affected (from your watchlist when given)'), which is real added semantic value; document_number is left to the schema's example and pattern.

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 deliverable for a specific resource: a 'structured, source-linked brief for one document' with an enumerated set of sections. It reads clearly as a retrieval/synthesis tool, but it never names a sibling (e.g., get_regulatory_document) to draw the line between a raw document fetch and a synthesized brief, so differentiation is left to inference.

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?

Usage is only implied: the agent can infer it should call this when it wants a single-document brief. There is no explicit when-to-use, when-not-to-use, or alternative routing among the many siblings (compare_regulatory_documents, get_regulatory_document, get_regulatory_timeline), and no stated prerequisites.

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