set_incomplete_delivery_location

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the tool replaces existing location, its reversibility, or error conditions (e.g., if full address already set).

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 short and front-loaded with the main purpose, followed by parameter list. Every sentence adds value, though the argument descriptions could be integrated more concisely.

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 the tool's simplicity (3 required parameters) and presence of an output schema, the description covers the basic action but omits important context about side effects, prerequisites, and error handling.

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?

With 0% schema description coverage, the description adds minimal context beyond the schema titles: 'cart ID', 'Delivery latitude', 'Delivery longitude'. It explains the purpose of the coordinates but lacks constraints like range or format.

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 'mark a cart for delivery with coordinates' and specifies the resource (cart with incomplete delivery location). It distinguishes from siblings like 'set_pickup_info' and 'add_address' by focusing on coordinates before full address.

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 implies usage when only coordinates are available ('before full address is set') but does not explicitly state when to use or avoid this tool, nor provide alternatives.

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