send_order_message

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

No annotations provided, so description carries full burden. It discloses that the message cannot be withdrawn or modified after sending, and that it adds a message to the buyer's inbox with immediate notification. This provides useful behavioral context beyond the schema.

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?

Description is efficiently structured with bullet points for usage, API, return, and side effects. It is front-loaded with the action and concise, though could be slightly more compact.

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 no output schema, description explains return structure (dict with success, resource_id, etc.) and side effects. It also provides the API endpoint. However, it lacks prerequisites (e.g., order existence) and does not clarify differentiation from 'send_shop_message'.

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 100% due to example within the schema itself. The tool description does not add new semantic information about the parameter; it merely restates example usage. Thus, no additional value is provided.

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?

Description clearly identifies the tool as sending order-related conversation messages to buyers. It specifies the verb 'send' and resource 'order message' and provides usage scenarios like order notifications and customer service replies. However, it does not explicitly distinguish from the sibling tool 'send_shop_message'.

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?

Description lists relevant use cases (e.g., shipping notifications, customer service replies) but does not specify when not to use or mention alternatives like 'send_shop_message'. It gives clear context but lacks exclusions.

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