Доставка: проверка кода [sandbox]

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is clear. The description adds no extra behavioral context (e.g., rate limits, authentication needs, or what happens when the code is incorrect). It is consistent with annotations but does not go beyond them.

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 very short (one sentence with sandbox tag), which is concise but lacking in substance. It repeats the tool name and title without providing additional useful information. It is not verbose, but it is under-informative for a tool that needs to guide correct invocation.

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?

The tool has no output schema, so the description should indicate what the tool returns (e.g., boolean, success/failure, or error messages). It does not. Additionally, it fails to differentiate from the similar sibling tool 'orders_check_confirmation_code', leaving the agent without sufficient context for correct selection.

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 input schema has 100% description coverage, with clear descriptions for both 'parcelID' and 'confirmCode'. The tool description adds no additional meaning, format, or constraints beyond the schema, so baseline score 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 the verb 'check' and resource 'parcel confirmation code', making the basic purpose understandable. However, it does not explicitly differentiate from the sibling tool 'orders_check_confirmation_code', which also checks a confirmation code but likely for orders.

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 provides no guidance on when to use this tool versus alternatives. Specifically, there is a sibling tool 'orders_check_confirmation_code' for checking order confirmation codes, but no distinction is made between delivery and orders contexts.

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