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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=true; they say nothing about cost. The description adds genuinely useful behavior: each successful call consumes 1 of the monthly quota, failed calls are not charged, and the result set is single-page. This is real value beyond the annotations, though return format and pagination/cache interaction are left to the schema.

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?

Dense and front-loaded: purpose first, then the two operational facts an agent most needs (single page, quota cost). The trailing 'GET /v2/search (ibp=htl;jobs)' is implementation trivia an agent cannot act on, the only wasted clause.

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?

For a six-parameter, no-output-schema search tool, the description covers the essentials: what is returned, that there is no paging, and the quota consequence of calling it. It is slightly thin on the cache/fields cost interaction, but an agent has everything needed to invoke it correctly.

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% and every parameter (q, gl, hl, cache, fields, location) is documented in the schema itself, so the baseline is 3. The description only echoes 'for a query' and adds no parameter syntax, defaults, or cross-references the schema lacks.

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 ('Google Jobs listings for a query') and even sketches the reply shape (jobs_results: title, company, location, source, apply url). It is unmistakably distinguished from siblings like zenserp_news_search, zenserp_video_search, or the generic zenserp_search without opening any schema.

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?

Gives a real usage constraint — 'do not repeat a call needlessly' and 'Google returns one page; there is no paging' — which tells the agent not to paginate or retry. However, it never states when to prefer this tool over siblings (e.g. the generic zenserp_search) or any explicit when-not condition, so guidance remains implied.

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