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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: each source degrades gracefully and a failing leg is noted rather than fatal, and the result is a narrative synthesis with a headline and four named sections.

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?

Though detailed, every sentence earns its place: scope, sources, output format, graceful degradation, sibling differentiation, and caveat are all covered without redundancy. The most important identity phrase is front-loaded in the first clause.

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?

Despite having no output schema, the description sufficiently characterizes the return value as a readable brief with a headline and four named sections. It also conveys source breadth, matching strategy, failure behavior, and informational nature, so an agent can correctly anticipate what the tool will do and produce.

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 schema fully documents company, ticker, and state. The tool description confirms the matching intent (e.g., SEC EDGAR match, name-matched federal awards) but does not materially expand parameter 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?

The description clearly states a specific verb and resource: it produces a one-call narrative public-record diligence dossier for a public company/SEC issuer. It enumerates the integrated sources and output structure, and explicitly distinguishes itself from counterparty_risk_score and entity_dossier, making sibling differentiation immediate.

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?

It names the closest sibling alternatives and states the key differentiator: this tool returns a narrative synthesis rather than a 0-100 score and covers more sources than the SEC+EPA+sanctions-only entity_dossier. It also declares what the tool is not (a background check or legal/financial advice), giving clear selection context.

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