send_buyer_message

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

The description only discloses that confirm=True is required to actually send the message. Since no annotations are provided, the description should also mention that the tool performs a write operation, any permission requirements, or what happens if confirm is false. This is insufficient for a mutation tool.

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 with two short sentences, front-loading the purpose. However, it could add more value without losing conciseness by explaining other parameters or usage conditions.

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 the 5 parameters and 0% schema coverage, the description is incomplete. It only addresses one parameter. While an output schema may exist, the description does not provide enough context for correct parameter usage or expected behaviors.

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%, yet the description only explains the confirm parameter. It does not clarify the meaning or constraints of body, order_id, message_type, or marketplace, which are critical for correct invocation.

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's purpose: 'Enviar mensaje al comprador' (Send message to buyer). It is specific about the resource (buyer) and action (send message). However, it does not differentiate from similar messaging tools like request_review, which also sends a message to the buyer.

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 notes that confirm=True is required, providing a usage condition. However, it gives no guidance on when to use this tool versus siblings like get_messaging_options or request_review, nor does it mention prerequisites or context.

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