avito_count_ads

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

Annotations already declare the operation as read-only, idempotent, open-world, and non-destructive. The description adds that it works 'sans connexion' (without login), which is useful context, but it does not describe return format, pagination, 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?

Two short sentences front-load the core action and include a specific usage tip. Every sentence earns its place with no filler.

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 tool with 19 parameters, low schema coverage, nested objects, and no output schema, the description is too sparse. It covers the high-level purpose and one parameter tip but leaves most filter semantics and expected output unexplained.

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 21% across 19 parameters, so the description carries a heavy burden. It only repeats the isPremium guidance already present in the schema and says 'filtres' generically, failing to compensate for the many undocumented parameters.

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 ('Compter') and resource ('annonces publiques') with the scope of filters and no login needed. It also names the sibling avito_search_ads and clarifies the relationship via isPremium:false, though it does not fully distinguish all counting scenarios from search.

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?

Provides a concrete instruction for one parameter: 'Utiliser isPremium:false pour compter le flux principal de avito_search_ads.' This implies the tool is for counting rather than listing, but does not explicitly state when to use it versus avito_search_ads or other alternatives.

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