amazon_check_delivery

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

With no annotations, the description carries full burden. It discloses the mechanism (Glow address-change call, reloading product HTML) which hints at read behavior, but does not state whether the address-change call has side effects, if authentication is required, or what the exact return format is. Partial transparency, but enough to understand the process.

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 two sentences with zero redundancy. The purpose is front-loaded, and the second sentence provides method context without fluff. Every word earns its place.

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?

An output schema exists, so return format is covered elsewhere. However, given the tool's complexity (uses HAR, address-change call), the description does not mention safety, authentication, or potential side effects. It is adequate for basic usage but not fully complete for a tool that performs a multi-step operation with possible mutation.

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 0%, so the description must add meaning. It specifies that pincode must be 6-digit and mentions ASIN, but does not explicitly explain that asin_or_url accepts a URL as well, nor does it clarify the URL format or any validation rules. It adds some value but does not fully compensate for the lack of schema descriptions.

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 action (check delivery ETA) and the specific resource (Amazon.in, ASIN, pincode). It is specific and distinct from sibling tools like search_products or get_product, which focus on discovery or product details rather than delivery estimates.

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 purpose implies when to use (when delivery ETA is needed), but the description does not explicitly contrast with alternatives or provide exclusions. It does not say 'use this instead of X' or mention scenarios where this tool would not be appropriate, leaving some inference to the agent.

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