Send Conversation

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

The description provides no additional behavioral details beyond the annotation's destructiveHint. It does not mention side effects like creating a conversation thread, sending notifications, or requiring specific permissions, which would be useful context.

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 a single, succinct sentence with no redundant wording, effectively conveying the tool's purpose without unnecessary detail.

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 tool's simplicity and the absence of an output schema, the description sufficiently covers the essential functionality without needing to explain return values or complex 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?

The input schema already includes concise descriptions for all three parameters (body, subject, recipients), and the description does not add any extra semantic meaning or clarify parameter relationships beyond what is already 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?

The description clearly states the action (send), the object (new conversation message), and the target (one or more recipients), making it unambiguous and distinct from sibling conversation tools that list or retrieve conversations.

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 implies when to use it (when sending a new message) and is straightforward, though it does not explicitly contrast with alternatives like replying to an existing conversation. However, the term 'new' clarifies the intended use case.

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