avito_public_search_link

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

Annotations already declare readOnly/idempotent/openWorld/destructive=false, so the safety profile is covered. The description adds genuinely useful context beyond them: the output is a link meant to be opened on the external Avito.ma site rather than returned data, which explains the openWorldHint and steers the agent away from expecting ad results.

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 tightly written sentences with the core action front-loaded and no filler. The second sentence is purely routing, which is worthwhile content but slightly displaces behavior about the built link.

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 simple two-parameter, no-output-schema builder tool, the description covers what it produces and where to go for actual results, and annotations cover safety. The missing piece is any description of the 'query' parameter or what the returned link looks like.

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 50% (citySlug is documented with slug examples, query is not). The description mentions no parameters at all, so it fails to compensate for the undocumented 'query' parameter (maxLength 200, format unknown). Marginal value over the schema.

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 and resource ('Construire un lien de recherche') and immediately distinguishes itself from siblings by naming avito_search_ads and avito_search_my_ads. An agent can identify this as a link-builder rather than a data fetcher without opening the schema.

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?

Explicitly routes the agent: to retrieve public ads use avito_search_ads, for account ads use avito_search_my_ads, implying this tool is for when you only need a shareable/openable link. Both alternatives and the selecting condition are named.

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