Массовое скрытие предложений

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

Annotations only provide hints (readOnly=false, openWorld=true), so the description carries the transparency burden. It adds response format ({ status: OK } or errors), specific error codes, TTL semantics (common ttl for all), and rate limit (50k/min shared with show_offers). Not exhaustive (e.g., no auth requirements or partial-failure behavior) but substantially transparent.

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 compact and front-loaded with the main action, then endpoint, TTL behavior, response format, and limits. Every sentence adds value with no redundancy or 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 complex batch tool with no output schema, the description covers the essential aspects: operation, limits, TTL behavior, response format, error codes, and rate limit. Minor gaps include explicit comparison to hide_offer and partial-failure semantics, but overall it is reasonably complete.

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 100%, so baseline is 3. Description adds meaningful nuance: 'Общий ttl_in_hours применяется ко всем предложениям запроса' clarifies that TTL is shared across all offers. Also includes error codes related to invalid parameters (e.g., INVALID_TTL, LIMIT_EXCEEDED).

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?

Description clearly states the tool's function: 'Массово скрывает предложения из Поиска' — mass-hides offers from Search. It specifies the scope (1–500 per request) and differentiates from the singular sibling hide_offer by the word 'Массово' and the batch size.

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 clear context: batch operation up to 500 offers, shared TTL, HTTP endpoint, and rate limit shared with show_offers. Excludes nothing explicitly but the mass nature makes it obvious when to use this instead of hide_offer. Lacks explicit 'use this for X, not Y' phrasing.

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