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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered and the bar is lower. The description does add real behavior context beyond them: results carry a build date and sources, and the call is free. It says nothing about result volume, pagination, or the shape of the payload, which matters for a program-wide sweep that could return many rows.

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?

The content is dense and mostly front-loaded, but it is written as a long run-on list of noun fragments with no governing verb, so the reader must infer that the call *returns* these findings. Asides like 'antennas and dollars' and 'With build date and sources. Free.' are tacked on rather than integrated. Nothing is clearly wasted, but the structure is list-dump rather than sentences.

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?

For a no-parameter, read-only tool with no output schema, the description covers what an agent needs: what the dataset is scoped to, the specific finding classes returned, provenance (build date, sources), and cost. The remaining omission is the response format and expected result size, which is a modest gap rather than a blocking one.

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 tool takes zero parameters, which is the baseline-4 case; there is no argument surface for the description to explain. The text also makes clear the call is unfiltered and program-wide, which implicitly confirms that no scoping arguments are needed.

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 names a specific resource ('program-wide findings on the real records the Upper C-band Clearinghouse will pay against') and enumerates concrete finding categories (call sign changes, control groups, duplicate dish filings, foreign-adversary flags, FAA expiry, co-owned aircraft, reused N-numbers). That is far more specific than the title, which merely restates 'integrity findings'. It never names a sibling, but the 'program-wide' framing implicitly contrasts with record-level siblings such as clearinghouse_record.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative despite the presence of clearinghouse_precheck, clearinghouse_validate, and clearinghouse_record in the same family. The agent must infer that this tool is the portfolio-wide integrity sweep rather than a per-record check. 'Free' hints that it costs no credits, but that is a cost signal, not a routing rule.

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