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

Annotations already declare readOnlyHint and openWorldHint (consistent with 'public Google web responses'). The description adds real behavioral context beyond the annotations, notably that nocache is restricted to admin/monitor keys, forces a fresh live render, and is ignored for other keys.

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?

Compact and front-loaded with the purpose, but the flow jumps from a nocache note to a page note to a sibling pointer without logical grouping. Most sentences earn their place, but the sibling sentence is arguably misplaced.

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 an output schema present, return values need not be described. All four parameters are covered by schema and description, and the read-only public-source nature is conveyed. The main gap is the unresolved ambiguity versus google_jobs_search.

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 all four parameters. The description restates the nocache and page semantics without adding syntax or format detail beyond the schema, so 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?

States a specific verb+resource: 'Returns normalized Google Jobs results parsed from public Google web responses.' It names the sibling google_jobs_search, but rather than distinguishing itself it directs the agent to that sibling, so the differentiation is muddled. The core purpose is still clear.

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 only guidance is 'Use google_jobs_search to retrieve google Jobs search,' which points to the sibling without explaining when this tool itself should be used. No when-to-use/when-not conditions for google_jobs are provided, leaving the agent uncertain about choosing between the two.

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