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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds non-trivial context the schema does not carry: it requires a Geonode API key sent as an X-Api-Key header, and results are paginated. It stops short of describing what a job record contains or how results are ordered.

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?

Three tight sentences with the core action front-loaded and pagination/auth folded in efficiently. No filler, though the status enumeration is the weakest sentence because it is inaccurate.

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 read-only listing tool with annotations covering the safety profile and no output schema, the description supplies the missing auth and pagination essentials. The main gap is that an agent gets no sense of the returned fields and no warning about the status-value mismatch with the schema enum.

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%, so the description carries the burden and does explain query as partial match and maps date range and page/page_size. But it misstates the status values ('pending, running' vs. the schema enum 'queued, processing, cancelled'), never mentions the api_key parameter directly, and omits the defaults (page=1, page_size=10) and the start_date/end_date parameter names.

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 opens with a specific verb+resource ('List search jobs') and states the scope ('for the authenticated user with optional filters'). It does not differentiate from the closely named siblings search_job, jobs, and job, so an agent cannot tell from the description alone which of those to pick.

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 gives usable context for how to filter (query partial match, status, date range) and how to paginate, which implies the usage scenario. However, there is no explicit when-to-use guidance and no mention of when to prefer search_job, job, or batch_status instead.

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