Avito Seller Profile

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds concrete error behavior — empty input, 404, transport blocks, and parser drift — plus a high-level response envelope. This is useful operational context beyond the annotations.

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 well-structured with the core purpose front-loaded, followed by context and then return/error formats. Every section serves a clear role; the classifieds context sentence is slightly explanatory but earns its place by clarifying the tool's value.

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 single-parameter read-only tool with full schema coverage, a rich output schema, and safety annotations, the description covers purpose, domain context, response shape, and error modes. Nothing essential for correct selection or invocation is missing.

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?

Input schema coverage is 100%, and the schema already describes seller_id_or_url as 'Seller id or profile URL from a card/search hit'. The description does not add parameter-specific semantics beyond framing the output as seller reputation data, so the baseline score is appropriate.

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 'Fetch an Avito seller profile', clearly identifying the action and resource. It then explains that the seller's rating, review count, and active-listing count are the relevant reputation signal for classifieds, which distinguishes this tool from per-item review or card tools.

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?

The description gives clear context for when to use this tool: when evaluating a seller's reputation in classifieds, since there is no per-item review pool. It does not explicitly name alternative tools or state when not to use it, but the domain context is strong enough to guide selection.

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