usajobs_search

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

The readOnlyHint annotation already establishes the tool as read-only. The description adds useful context by listing the returned fields (position titles, agencies, locations, salary ranges, application deadlines), which helps the agent understand the output shape despite the absence of an output schema. No additional behavioral traits like pagination or rate limits are disclosed, but the description aligns with the annotation.

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 two concise sentences that front-load the purpose and then state the return fields. It is efficient, with no wasted words.

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?

The description covers the tool's purpose, filters, and return values. Since there is no output schema, listing the returned fields is essential and it does so. It does not mention optional implementation details like the limit parameter's default or pagination, but these are available in the schema and not critical for basic usage.

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 all six parameters are individually documented in the schema. The tool description summarizes the main filter types (keyword, location, agency, salary range) but adds no new syntax or format details beyond the schema. This meets the baseline of 3.

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 uses a specific verb ('Search') and resource ('federal job listings on USAJobs.gov'), and lists the key filter dimensions (keyword, location, agency, salary range). It clearly distinguishes the tool from siblings like usajobs_detail by focusing on search behavior.

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 no information about when to use this tool versus alternatives such as usajobs_detail. There are no explicit use cases, exclusions, or references to sibling tools, leaving the agent to infer appropriateness from the name alone.

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