Доставка: массовое обновление [sandbox]

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

Annotations already provide readOnlyHint, destructiveHint, and idempotentHint. The description adds no behavioral traits beyond the sandbox context. It does not disclose what gets updated, side effects, or required permissions, adding minimal value.

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, very concise and front-loaded. However, it may be too brief, trading completeness for brevity.

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 no output schema and 4 parameters (including a complex 'applications' array and a 'type' string with no enums), the description is insufficient. It does not explain what types are available, the structure of applications, or what the tool returns. The agent lacks key context for correct usage.

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 description is not required to explain parameters, but it adds no extra meaning. It merely restates the action; the schema itself provides descriptions for each parameter. Adequate but not improved.

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 states 'mass update of parcel properties' which gives a verb and resource, but it is vague: it does not specify which properties are updated or differentiate this sandbox tool from the real delivery_v1_change_parcel. It is clear enough but lacks detail.

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?

There is no guidance on when to use this tool versus siblings like delivery_v1_change_parcel or delivery_change_parcel_result. No when-not or alternative tools are mentioned, leaving the agent without decision context.

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