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

With no annotations, the description carries the full burden. It usefully discloses that next_url is opaque, that this is Nova LD pagination, and that a prior search/session is involved, but it does not describe failure behavior for an expired or invalid next_url, nor does it clarify whether this is a safe read operation.

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?

It is a single concise sentence with no filler. The key dependency and pagination mechanism are front-loaded, making it easy for an agent to scan.

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 simple pagination tool, the description covers the core dependency and pagination source. However, with no annotations and no output schema, it could better explain error/expiry behavior and how the optional notification_message parameter is intended to be used.

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 coverage is 100%, so both parameters are already documented in structured form. The description adds context for next_url by calling it opaque and tying it to the prior search, but it does not mention notification_message or add syntax details beyond the schema.

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 uses a specific verb and resource ("Fetch the next Jiji ads_listing page") and identifies the continuation mechanism ("opaque next_url from the prior search"). That clearly separates it from initial search tools like search_listings, though it does not name a sibling alternative 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?

It states the tool should be used with the next_url from a prior search and references the session fallback via the schema. The usage context is clear, but there are no explicit exclusions or named alternatives for non-pagination cases.

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