alonomic_update_parcel

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

Warns about destructive nature upfront, explains API endpoint, specifies that only passed fields are sent, and describes error behavior. With no annotations, the description effectively discloses key behaviors.

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?

Well-structured with warning, purpose, and Args section. Persian translation is slightly extraneous but not detrimental. Generally 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?

Covers mutation behavior, prerequisites, error handling, and parameter roles. Output schema exists, so return values need not be detailed. Complete enough for effective tool 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?

Lists all parameters with brief descriptions (e.g., 'Numeric id', 'Optional updated drop-off object'). Schema coverage is 0%, so description adds some meaning but lacks details about object structures.

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?

Clearly states 'Update a parcel before final send' with a warning that it changes a real parcel. Maps to PUT endpoint. Distinguishes from siblings like create_parcel and cancel_parcel.

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?

Explicitly states prerequisites (Alonomic credentials, enable_ordering=true, read_only=false) and notes error condition if disabled. Does not explicitly name alternative tools but provides clear context.

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