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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description goes meaningfully beyond them by disclosing the paid nature: '$0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.' That billing behavior is important for an agent to know before invoking. It does not cover rate limits, empty-result behavior, or truncation beyond '10 per page'.

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 core content is front-loaded and dense, which is good, but the single long sentence is a run-on, and the sibling-routing clause contains a visible truncation ('We Work Remotely's public.') plus bulky parentheticals. The routing sentences consume space disproportionate to their usefulness.

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?

An output schema exists, so return values needn't be explained, and pricing/payment plus sourcing from the public search results page are covered. The remaining gap is differentiating this from the closely related jobs_usajobs federal listing tool, which the description never mentions.

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 already documents keyword, location, and the page range (1–20). The description repeats 'a keyword and optional location' and '10 per page' without adding format, normalization, or matching 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 names a specific verb+resource+scope: 'US public-sector job postings from GovernmentJobs.com (NEOGOV; state, county, city and agency jobs)' for a keyword and optional location. It enumerates the returned fields (title, agency, location, job type, salary range, closing note, featured flag, URL) and the page size, so an agent knows exactly what it is getting.

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 implied by the scoping phrase 'US public-sector' and the explicit 'Related tools ... for a different need' routing to jobs_wantedly and jobs_weworkremotely. However, the two alternatives offered are not the closest competitors — jobs_usajobs (federal jobs) and other general boards are not addressed, and there is no explicit when-to-use/when-not statement.

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