USAJOBS Federal Job Search

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating safe read-only operation. The description adds context about USAJOBS being the sole source for federal postings but doesn't disclose additional behavioral traits like rate limits or pagination beyond what the schema provides. No contradiction with annotations.

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 description is exceptionally concise – two sentences that perfectly convey purpose, scope, and exclusivity. No unnecessary words, and the most critical information is front-loaded.

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?

Given the presence of a complete output schema, thorough annotations, and full parameter documentation, the description provides sufficient context for a search tool. It could mention rate limiting or error handling but those are common and not critical for selection.

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 input schema already has 100% description coverage for all 8 parameters, including examples and formats. The tool description briefly lists search criteria but adds no new semantic information beyond the schema. Thus it meets the baseline without additional value.

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 the tool's function: searching US federal civil-service job postings by various criteria (keyword, location, pay grade, agency, position type). It also explicitly distinguishes this tool from other job search services like BLS, ESCO, CareerJet, etc., making the purpose unambiguous.

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 description provides explicit guidance on when to use this tool (for US federal civil-service jobs) and when not to (for non-federal jobs, listing alternative job services). This helps the agent select the correct tool among the many job-related siblings on the server.

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