delete_offer

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

Annotations already mark destructiveHint: true. The description adds 'ВНИМАНИЕ: необратимое действие' (WARNING: irreversible action), which emphasizes the destructive nature and adds behavioral context beyond annotations. It also mentions return value (confirmation), but does not detail other effects.

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 concise (3 sentences plus a warning) and well-structured: purpose, usage, return value, warning, related tool. Every sentence adds value with no wasted words.

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 tool with one parameter, destructive behavior, and an output schema, the description covers all necessary aspects: purpose, usage context, irreversibility, return value, and related tool. It is complete and leaves no significant gaps.

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?

Only one parameter (offer_id) with 0% schema description coverage. The description does not add any additional meaning beyond the schema. However, the parameter name is self-explanatory, and the tool context makes it clear. A minimal viable score is appropriate since no parameter info is provided in the description.

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 'Удалить ваше предложение с биржи Kwork' (Delete your offer from Kwork exchange), which is a specific verb+resource. It distinguishes from sibling tools like submit_offer (create) and list_my_offers (list).

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 states when to use ('для отмены отправленного предложения' - to cancel a submitted offer) and provides a related tool (list_my_offers) to help find the offer ID. This gives clear guidance on when to use this tool vs alternatives.

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