⚠️ Доставка: создать посылку [3PL]

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which align with creation. The description adds no behavioral details beyond what annotations provide (e.g., side effects, error handling, or dry run behavior, though dryRun is documented in schema).

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?

Two sentences effectively convey purpose and required/optional structure. No extraneous information. Front-loaded with the core action.

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?

Despite 12 parameters and nested objects with no output schema, the description omits return values and behavior. Relies on external swagger file for nested objects. Insufficient for an agent to fully understand invocation outcome.

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 coverage is 100% with descriptions for all 12 parameters. The description lists required and optional fields but adds little extra meaning, relying on schema definitions. Nested objects are referenced to an external file, which is helpful but not embedded.

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 it's for 3PL partner parcel creation and lists required/optional fields. It specifies the business context (3PL) which helps distinguish from other delivery tools, though it does not explicitly compare to siblings.

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 lists required and optional fields but provides no guidance on when to use this tool versus alternatives like delivery_create_announcement_3pl or delivery_v1_create_announcement. No context on prerequisites or when to avoid.

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