ozon_action_auto_add_candidates

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

With no annotations, the description carries the full disclosure burden, but it does not state whether the operation is read-only, what it returns, whether it has side effects, or how pagination behaves. The noun-phrase description does not even confirm the operation being performed.

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 extremely short, but this is under-specification rather than helpful conciseness. The '[P0]' prefix adds operational noise, and the core semantic content is missing.

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 tool with no annotations, no output schema, four parameters, and a large sibling group, a one-phrase description is far from sufficient. Missing information includes the operation, return behavior, pagination semantics, and the tool's role in the auto-add workflow.

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 description coverage is only 25%, and the description adds no parameter explanations. The meaning of action_id, limit, offset, and auto_add_date in the context of automatic addition is left entirely to inference.

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 is a noun phrase that largely restates the tool name: 'candidates for automatic addition to a promotion.' It names the resource but provides no verb or operation, and it does not distinguish this tool from siblings like ozon_actions_candidates, ozon_action_auto_add_products, or ozon_action_auto_add_delete.

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?

No guidance is given about when to use this tool versus related auto-add or action tools. There is no context, prerequisite, or mention of alternatives.

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