Создать аккаунт в песочнице

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

Annotations already mark readOnly=false, idempotent=false, and destructive=false. The description adds substantial behavioral detail: environment-gated rejection, empty-contact pre-validation, non-idempotency, account immutability, and the fact that the new accountID is not automatically picked up by AVITO_ADS_ACCOUNT_ID and must be configured manually.

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 dense and front-loaded with the most important constraint (sandbox-only) and the core purpose. Every sentence adds a distinct behavioral fact, and the length is justified by the number of non-obvious side effects.

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 mutating tool with 9 parameters and no output schema, the description covers the return value, environment prerequisite, validation behavior, idempotency, immutability, and configuration follow-up. The schema covers parameter details, so nothing critical is missing.

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 100%, so the baseline is 3. The description reinforces the contact object requirement with an example and adds that an empty contact is rejected before the request, but it does not add meaning for the other eight parameters beyond what the schema already provides.

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 opens with 'ТОЛЬКО ПЕСОЧНИЦА' and clearly states that the tool creates a test advertiser account and returns its accountID. This is a specific verb+resource with an explicit environment scope, distinguishing it from sibling tools like create_advertiser or create_child_account.

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 explicitly says the server rejects the call unless AVITO_ADS_ENVIRONMENT=sandbox and that such a refusal does not count against the API quota. This provides clear when-to-use context, though it does not name a non-sandbox alternative tool.

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