flipkart_manage_shipments

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

With no annotations, the description must disclose behavioral traits. It mentions actions and output format (Markdown or JSON) but lacks details on authorization needs, error handling, or side effects (e.g., consequences of cancellation). The description is adequate but not comprehensive.

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 concise and well-structured with a clear header, bulleted actions, and a note on output format. It front-loads the purpose and is devoid of unnecessary words.

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 6 parameters, 0% schema coverage, and no annotations, the description provides a solid overview. It covers all actions and hints at parameter usage. However, it lacks examples, error scenarios, or detailed parameter constraints. An output schema exists but is not described.

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 description coverage is 0%, so the description should compensate. It explains parameters like state (via action descriptions), order_id, detail_level, shipment_ids, and cancel_reason. However, it does not detail all parameters or their valid values (e.g., allowed states or cancel reasons). The description adds some meaning but not enough to fully cover all 6 parameters.

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 tool manages shipments and orders for Flipkart sellers, listing specific actions like search, inspect, mark_rtd, get_label, and cancel. This distinguishes it from sibling tools like flipkart_manage_returns or flipkart_manage_inventory.

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 implicitly guides usage by enumerating actions and their brief purposes (e.g., 'search: List pending, packed, RTD, or dispatched orders'). However, it does not explicitly state when to use this tool over alternatives or provide exclusion criteria.

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