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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the backing endpoint, which hints this is a read-only fetch, but says nothing about auth requirements, error behavior when the id is invalid, or what the response contains. The required notification_message parameter's failure semantics are also unexplained.

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 tight sentence with the verb and route front-loaded; no filler. It is arguably too terse rather than padded, and the parenthetical route note is the only marginally expendable element.

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?

With no annotations and no output schema, the description is the only place an agent can learn what this returns or how it differs from three similarly named siblings, and it supplies neither. For a simple two-parameter fetch the gaps are recoverable but real.

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%, so both parameters are already documented ('Numeric advert id from search results[].id' and the plain-text fallback sentence). The description adds no parameter meaning beyond the schema, which is acceptable at full coverage but earns only the baseline.

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 names a specific verb and resource ('Fetch Jiji advert') and pins the underlying route (api/v2/advert/{id}, mobile app detail route). However, three siblings (view_listing_advert, view_listing_detail, view_listing_v2) do nearly the same thing, and nothing in the description tells an agent which one to pick. The purpose is intelligible but not disambiguated.

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?

'(mobile app detail route)' is a technical annotation on the endpoint, not guidance on when to use this tool over view_listing_advert or view_listing_detail. No prerequisites, no exclusions, no alternative named.

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