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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds the returned field set, but omits behavior that matters for a search tool: ordering of results, whether unfiltered calls return the whole corpus, and any paging ceiling beyond the schema's 1-500 hint.

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?

Two short sentences, correctly front-loaded with the action before the return payload. The second sentence slightly duplicates what the output schema already exposes, but it is brief enough not to be wasteful.

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?

With nine optional parameters, no required fields, and a rich annotation set, the description is thin: it never says what happens when no filters are supplied or how results are ordered/paged. The output schema and 89% schema coverage relieve most of the burden, so this is adequate but leaves real gaps.

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 89%, so nearly every one of the nine parameters is already documented, including keyword scope and pay grade formats. The description contributes no additional parameter meaning, which puts it at the baseline for high-coverage schemas.

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 verb and resource ("Search USAJOBS announcements") and even names the fields returned, so an agent knows immediately this is a keyword/filter search over federal job postings. It does not distinguish itself from usajobs_get_job, so an agent cannot infer from the description alone when to search versus fetch a single posting.

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?

There is no when-to-use guidance, no statement of prerequisites, and no routing to alternatives such as usajobs_get_job or usajobs_list_agencies. Usage is only implied by the verb "Search".

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