Bulk Import BlueDart Waybills

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

Description adds that partial successes are possible and returns per-shipment results, which goes beyond annotations. Annotations already indicate destructive and non-idempotent behavior.

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?

Extremely concise: three sentences with no waste. Essential info front-loaded: purpose, endpoint, relation to sibling, partial success.

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 one parameter with full schema description, no output schema, and sibling tools, the description covers key aspects. Could mention prerequisites or error handling, but annotations fill gaps.

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 covers the shipments parameter with min and max items. Description does not add extra meaning beyond what schema provides, so baseline 3 due to high schema coverage.

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 the tool creates multiple waybills in a single request. Distinguishes from sibling by noting each entry has same shape as bluedart_generate_waybill.

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?

Clearly indicates batch operation, implying it for multiple waybills. Notes relation to sibling but does not explicitly state when to choose this over alternatives.

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