Доставка: статус задачи [sandbox]

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

Annotations declare it as read-only, non-destructive, idempotent, and open-world. The description adds context that it operates in a sandbox and uses async operation task IDs, which aligns 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 short sentence, conveying the essential purpose without extra words. It is front-loaded and efficient.

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?

No output schema exists, and the description does not indicate what information is returned (status, result, etc.). For a tool that retrieves async task status, this is a significant gap.

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 provides full description for the single parameter (task_id). Description does not add additional semantics beyond what the schema already states.

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 retrieves information about a task from async operations in a sandbox environment. It distinguishes itself from siblings by specifying 'taskID from async operations', which is a unique identifier among delivery tools.

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 explicit guidance on when to use this tool versus alternatives. It implies it's for checking async task status, but does not mention conditions or common sibling tools like delivery_tracking or delivery_sandbox_track_announcement.

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