send_order_to_vendor

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

Discloses the key non-obvious behaviors: item matching uses the products' current vendor routing, and Fulfillment Test Mode redirects the email to the merchant with a [TEST] banner. These add value beyond the annotations, which only indicate readOnly/idempotent/destructive false.

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?

Three purposeful sentences: main action, usage distinction, and test-mode caveat. No filler or repetition.

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?

Covers the main action, applicable scenarios, and an environment-specific caveat. It does not describe return values or error conditions, but the simple 2-parameter schema and absent output schema reduce the burden.

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?

The schema has no descriptions for orderId/vendorId, but the description maps them to 'an existing order' and 'a vendor.' The routing explanation adds context around how vendor matching works, though it stops short of stating parameter formats or constraints.

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 opens with 'Manually email an existing order to a vendor,' giving a specific verb and resource. It also distinguishes manual sends from automatic sends at payment, so sibling tools are clearly differentiated.

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?

States exactly when to use: orders placed before vendor setup and deliberate re-sends. It explicitly contrasts with the automatic email path, telling the agent when the tool should not be used.

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