etsy_receipt_shipment_create

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

With no annotations provided, the description must fully disclose behavior. It only states the action without mentioning side effects (e.g., whether it replaces existing tracking, whether it sends notifications, or what constitutes a shipment). Does not disclose if the operation is reversible or if there are rate limits.

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?

Single sentence, directly to the point with no fluff. Every word is necessary. Efficiently communicates the core purpose.

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, no output schema, and no annotations, the description is insufficient. It fails to explain what the tool returns (e.g., created shipment ID or success status), how it interacts with existing shipments, or any constraints like maximum tracking codes per receipt. The high parameter count and complexity demand richer contextual information.

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 50% (3 of 6 params have descriptions). The tool description adds no additional meaning beyond the schema. For parameters like shop_id and receipt_id, no guidance is given on format or acceptable values. The description does not compensate for the schema gaps.

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 'Create a shipment / add tracking to a receipt' clearly states the action (create/add) and the resource (shipment/tracking for a receipt). It distinguishes from siblings like etsy_receipt_shipments_list which lists existing shipments, making the tool's purpose specific and unambiguous.

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?

No guidance on when to use this tool vs alternatives (e.g., adding tracking vs. creating a shipment separately). Doesn't mention prerequisites like requiring an existing receipt or the need for a carrier name and tracking code. No exclusions or warnings about overwriting existing tracking.

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