Get an Avito listing

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds the useful fact that a seller profile is bundled in, but it discloses nothing about auth/session requirements, behavior when the listing id is invalid or removed, or rate limits.

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?

One front-loaded sentence that opens with the verb and resource. The long field enumeration is slightly list-heavy but justified since no output schema exists to convey the return shape.

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 one-parameter read tool with no output schema, describing the returned fields is exactly the right compensation. It stops short of covering error/not-found behavior and the session prerequisite implied by the sibling avito_setup_session.

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% and the single 'item' parameter already documents both the URL form and numeric id, so the description adds nothing beyond the schema. Baseline 3 is appropriate when the schema fully carries parameter meaning.

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 ('Get') and resource ('one Avito listing') and enumerates the returned fields, making the single-item lookup role clear. It implies contrast with avito_search but never names or explicitly differentiates from that sibling.

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?

'Get one' hints that this is single-item retrieval versus a search, but the description never states when to use it over avito_search or avito_seller_reviews, nor any prerequisites such as needing an authenticated session from avito_setup_session.

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