Обновить объявление

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

Annotations already provide idempotentHint=true and openWorldHint=true. The description adds valuable behavioral context: the changed ad goes to moderation. This is not in annotations and helps the agent understand consequences beyond the structured fields.

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 with clear, front-loaded purpose. Every word is informative with no fluff.

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 update tool with 5 parameters, annotations covering idempotency and open world, and no output schema, the description is mostly complete. It explains the moderation effect, which is crucial context. Minor gap: no mention of what happens to omitted fields (likely unchanged due to idempotentHint).

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 descriptions cover all 5 parameters with details (e.g., max lengths). The description repeats 'заголовок, текст, ссылка' but omits 'title2' and provides no additional semantic meaning beyond the schema. Since schema coverage is 100%, baseline is 3.

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 clearly states the verb 'обновить' (update) and the resource 'текстовое объявление' (text ad), listing the updatable fields (заголовок, текст, ссылка). It distinguishes from the sibling tool 'create_text_ad' by focusing on modification rather than creation.

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?

The description implies when to use (update an existing ad vs. create a new one) but does not explicitly state usage context, prerequisites, or when not to use. It lacks guidance on alternatives like delete or manage_ads.

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