avito_search_my_ads

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

Annotations already declare the read-only, idempotent, non-destructive profile, so the safety burden is lifted. The description adds one real behavioral note ('Conserve adId et listId distincts'), which warns about identity handling in results, but says nothing about pagination semantics or result size.

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 compact sentences, filter scope front-loaded, with the facet dependency and the adId/listId caveat trailing appropriately. No padding.

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 an 11-parameter tool with 18% schema coverage and no output schema, the description covers the main filter axes and the facet sourcing but omits pagination controls, keyword, boosted, and the status enum. Adequate but with clear gaps.

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 only 18%, so the description must compensate. It names the filter families (statut, catégorie, ville, prix, paramètres, type) and explains that params/adTypes come from facets, but leaves keyword, boosted, page, and pageSize undocumented and does not enumerate the status values.

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 (Rechercher) and resource (annonces du compte) plus the filter dimensions covered. The qualifier 'du compte' implicitly separates it from the public avito_search_ads, but no sibling is named 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?

Gives one actionable directive — consult facets for filter IDs, pointing at avito_get_my_ads_facets — but says nothing about when to prefer this over avito_search_ads, avito_count_ads, or avito_get_my_ad, and offers no exclusions.

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