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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context that no login or account is required and that pagination follows next cursors, though it does not discuss rate limits or result behavior.

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?

The description is short and front-loaded, with the core action stated first. 'Call directly for job searches' is somewhat redundant with the opening sentence, but overall it is efficient.

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 nine-parameter search tool with no schema parameter descriptions, the definition is incomplete. It covers authentication and pagination but leaves the agent without guidance on the available filters and sorting options, even though an output schema exists for return values.

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 nine parameters, so the description must compensate but largely does not. It only indirectly explains the cursor parameter via 'Follow next cursors to paginate' and says nothing about q, sort, limit, remote, salary, company, location, or profession.

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?

The description states a specific verb and resource: searching Autojob jobs. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as find_matches or get_job.

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?

It says to call directly for job searches and notes that no login or account is needed, which gives basic usage context. However, it does not state when to use this instead of alternatives like find_matches or get_job, nor does it describe exclusions.

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