start_kwork

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

Annotations only provide 'openWorldHint: true', so the description must carry the burden. It discloses that activation makes the kwork visible and returns a confirmation or error. However, it does not detail authentication requirements, idempotency, rate limits, or what happens if the kwork is already active, leaving some behavioral gaps.

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 well-structured with sections for purpose, usage, returns, and related tools. It is concise, front-loaded with the primary action, and every sentence adds value without redundancy.

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?

Given the low complexity (one parameter, simple action) and the presence of an output schema, the description is mostly complete. It covers the main use case and returns, but lacks parameter documentation and error details. The inclusion of related tools compensates slightly for the simplicity of the tool.

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 0%, and the description provides no explanation of the 'kwork_id' parameter. The agent must rely solely on the parameter name, which is meaningful but lacks additional context such as format, validation rules, or how to obtain the ID.

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 tool activates a paused kwork and makes it visible to buyers. It distinguishes from sibling tools like pause_kwork (the inverse) and list_my_kworks, making the purpose specific and unambiguous.

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 includes a 'Когда использовать' section explicitly stating when to use the tool: to resume showing a kwork after a pause. It also lists related tools. However, it does not explicitly state when not to use it (e.g., if the kwork is already active), though this is implied.

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