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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description usefully adds that postings are public and that chunks of the posting body (description/qualifications) come back inline, but says nothing about pagination behavior or result limits.

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?

A single front-loaded sentence that identifies source, scope, and returned content with no filler. Efficient, though it omits anything about the non-q parameters.

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-value explanation is rightly omitted, and the read-only annotations cover safety. However, for a search tool with a 0%-documented schema, the description does not compensate on parameter meaning, leaving it only minimally viable.

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 0% and there are three parameters. The description only obliquely implies that q is a full-text query; page and location are completely undocumented in either schema or description, leaving the agent to guess their format.

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 (search) and resource (Google Jobs postings) and pins the scope to careers.google.com's public postings, plus notes that inline description/qualifications are returned. This distinguishes it reasonably from the sibling google_jobs_job (detail fetch), though it never names that sibling explicitly.

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 word 'search' implies this is the discovery entry point versus google_jobs_job, but there is no explicit when-to-use, when-not-to-use, or named alternative. Guidance is only inferable from the verb.

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