Массовое создание почтовых ящиков

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

Annotations already declare destructiveHint=false and readOnlyHint=false. The description adds that it returns a list of created mailboxes and an array of errors, which hints at partial-failure behavior. However, it does not disclose rate limits, maximum batch size, or authentication requirements.

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 concise sentences, front-loaded with the action ('Создаёт сразу несколько...') followed by return-value behavior. No filler or redundant information.

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 batch creation tool without an output schema, the description gives essential return information (created list and errors) and API version. It lacks edge-case details like partial-failure semantics or size limits, but given the rich schema and sibling differentiation, it is almost 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 schema covers 100% of parameters with detailed descriptions, including required 'domain' and 'mailboxes' array with nested properties. The description adds no extra parameter semantics, so the baseline of 3 is appropriate.

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 that the tool creates multiple mailboxes at once on a single domain. It specifies 'API v2', distinguishing it from sibling tools like batch_create_mailboxes_v1 and create_mailbox. The verb 'Создаёт' and resource are explicit.

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 usage for batch creation on one domain, but it does not explicitly mention alternatives or when not to use it. It lacks a direct comparison with create_mailbox or batch_create_mailboxes_v1.

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