avito_get_my_ads_facets

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, covering the full safety profile. The description adds no behavioral context beyond this — no mention of pagination, rate limits, or what the counters represent. It essentially restates the purpose without new behavioral value.

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 clean, front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification rather than disciplined conciseness.

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, zero-required, no-output-schema tool with 18% schema coverage, one sentence is inadequate. An agent lacks the detail needed to invoke it correctly, especially around the params/adTypes cross-references the schema alludes to.

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 only 18%, so the description must compensate for 11 largely undocumented parameters, but it says nothing about page, pageSize, status, priceMin/priceMax, cityIds, etc. The vague word 'filtres' loosely maps to the params concept but adds no usable semantics.

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 states a specific verb and resource ('Lire les filtres et compteurs disponibles pour les annonces du compte'), making clear it returns facet/aggregation data rather than ad listings. However, it offers no differentiation from close siblings such as avito_search_my_ads or avito_count_ads, which the agent must infer.

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?

There is no guidance on when to use this tool versus the many search/count siblings. No prerequisites, no conditions, no alternatives are named, leaving the agent to guess from the name alone.

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