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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavioral facts — that nothing is persisted, that the call is free, and that results come back as pass/warn/fail per rule with verdict and preliminary payment amount. It stops short of stating rate limits or how many rules are evaluated.

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?

Almost all content is load-bearing, but it is delivered as one extremely long run-on sentence with semicolons and parentheticals, making it hard to scan for the lumpsum branch versus the altimeter branch. Bullet-style or sentence-split structure would materially improve parseability without adding length.

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 12-parameter tool with no output schema, the description covers both input branches, the authoritative sources consulted, the return shape (per-rule pass/warn/fail plus reason and compared record), the aggregate verdict, and the amount basis. Only edge-case behavior (e.g., how unknown or missing records are treated) is left unstated.

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 only 8%, so the description must carry the parameter burden and it does: it groups parameters by kind, gives the 'ID=qty|ID=qty' syntax for antennas, and supplies enum values (antenna_type single|multi|smb|lmb|gateway|tfe, retrofit_type upgrade|replacement) that appear nowhere in the schema. It also marks serial as optional, which the schema's required list alone would not make obvious.

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 opens with a specific verb and resource: 'Validate one FCC Upper C-band claim before it is filed', and then enumerates the two claim kinds (lumpsum, altimeter) and the data sources each is checked against. This is far more specific than a name restatement. It does not, however, distinguish itself from the sibling clearinghouse_validate or clearinghouse_record, leaving the precheck-vs-validate boundary 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?

The phrase 'before it is filed' and 'Nothing is recorded. Free.' imply this is a non-committal dry run, which is useful usage context. But there is no explicit statement of when to use this versus clearinghouse_validate or clearinghouse_record, and no stated prerequisites (e.g., must the claim already exist in the system).

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