Доставка: создать анонс [sandbox]

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

The description adds only the sandbox context; annotations (readOnlyHint=false, destructiveHint=false) indicate a non-read, non-destructive write, but the description does not disclose side effects, such as whether the announcement is immediately visible, requires confirmation, or triggers external API calls. No contradiction with annotations.

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 a single sentence, front-loaded with [SANDBOX]. It is concise but overly brief, sacrificing detail. While it avoids fluff, it does not earn its place by providing sufficient guidance.

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 complexity (9 parameters, nested objects, no output schema) and sibling tools, the description is inadequate. It fails to explain what an announcement is, the effect of creation, or the return value. The [SANDBOX] tag is a small hint, but context is incomplete for effective tool use.

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 67%, so the schema partially documents parameters. The tool description itself adds no parameter-level information, leaving that to the schema. The dryRun and idempotencyKey have their own descriptions, but the overall description does not explain how parameters relate to the action.

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 verb 'creating' and the resource 'announcement' in the sandbox environment. The [SANDBOX] prefix distinguishes it from non-sandbox announcement creation siblings like delivery_create_announcement_3pl and delivery_v1_create_announcement. However, it does not define what an 'announcement' is in this context, which limits clarity.

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 [SANDBOX] tag implies it is for testing, but there is no explicit guidance on when to use this tool versus other announcement creation tools (e.g., delivery_create_announcement_3pl for real orders). No when-not-to-use or alternative recommendations are provided.

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