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

Annotations only declare read-only and open-world, so the description carries most of the burden and does: it discloses the fixed 20-per-page pagination, the total match count, the field set returned, and — critically — a paid-access model ($0.002 USDC via x402 on Base/Solana/Arc, failures not charged). Auth/payment cost is exactly the kind of context annotations cannot express.

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?

Front-loads the resource and scope, then packs output fields, pagination, and pricing into two sentences with no filler. The field enumeration is dense but each item is concrete; only the overlap with the output schema makes it slightly longer than strictly necessary.

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?

Covers scope, input, output shape, pagination, and the unusual payment prerequisite — the last being the piece an agent could not infer from schema or annotations. With an output schema present, the field listing is a bonus rather than a gap-filler.

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 coverage is 100%, so both parameters are already documented. The description adds only the fixed page size of 20, which gives useful context for the 'page' parameter, but nothing about keyword syntax or matching behavior. Baseline 3 for a schema-complete tool is appropriate.

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?

States a specific resource (ClearanceJobs postings), the input (a keyword), and a precise scope: US defense/intelligence roles requiring a security clearance. That niche framing alone separates it from generic boards like jobs_indeed or jobs_dice without opening any schema.

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 domain constraint ('US defense and intelligence jobs that need a security clearance') plus 'From the public search page' gives a clear picture of when this tool applies, and the results shape (20/page, total count) implies the browsing workflow. It stops short of naming alternatives or exclusions, so it lands at 4 rather than 5.

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