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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context — that the source is credential-free public JSON and that results include inline description/qualifications — but says nothing about pagination, rate limits, or result size.

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 names the tool, its method, and its data source with zero waste. Nothing to trim.

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 values need not be explained, but for a six-parameter search tool with no schema descriptions and no usage guidance, the definition leaves the agent guessing about filters and paging. The data-source detail is helpful but insufficient.

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% across all six parameters (q, page, sort, limit, country, category). The description implies 'q' is a full-text query but provides no syntax, valid values, or defaults for sort, country, category, page, or limit, so it fails to compensate for the schema gap.

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 ('full-text query across amazon.jobs') and adds the underlying data source ('credential-free public careers JSON, including inline description/qualifications'). This distinguishes it reasonably from amazon_jobs_job and amazon_jobs_categories, though it never names those siblings 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?

No when-to-use guidance at all. It does not say when to pick this over amazon_jobs_job, amazon_jobs_categories, or the many other *_jobs_search tools (google_jobs_search, apple_jobs_search, indeed_search). The agent must infer usage entirely.

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