pause_kwork

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

Description discloses that the tool will stop the kwork from being displayed, which aligns with annotations (destructiveHint=true). It adds that this is a temporary hide. No contradiction, but could elaborate on reversibility. Annotations already set expectations.

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?

Description is very concise: two sentences plus a usage note and sibling reference. Essential information is front-loaded, with no unnecessary 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 toggle tool with one parameter and an output schema (not shown but implied), the description covers purpose, usage, and outcome. The only gap is parameter documentation, but overall it's fairly 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?

The single parameter `kwork_id` is required but has no description in the schema (0% coverage) and the tool description does not clarify what it represents or where to obtain it. The agent may need to infer its meaning from context.

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 action: 'Приостановить кворк' (pause kwork) and explains the effect: the kwork stops being displayed to buyers. The verb+resource is specific, and it distinguishes from sibling tool `start_kwork`.

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 provides usage context: 'Когда использовать: для временного скрытия кворка (отпуск, перегрузка)' and mentions the related tool `start_kwork` to resume. This clearly indicates when and when not to use.

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