send_message_to_address

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

Adds context about creating new chats and service defaults beyond annotations, but does not disclose potential risks like costs or address validation. The openWorldHint already covers external interaction.

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?

Concise two-paragraph format with clear arg list. Purpose is front-loaded, no redundant information.

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 purpose, parameter details, and behavioral context for a simple tool with three params and an output schema. No significant gaps.

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?

Description provides meaningful explanations for each parameter (e.g., address format, service options) beyond the schema, compensating for 0% schema description coverage.

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?

Clearly states the tool sends a message to a phone number or email and creates a new chat if needed. This distinguishes it from sibling tools like 'send_message' which likely require an existing chat.

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?

Implies when to use by describing the behavior of creating a new chat, but does not explicitly state when not to use or contrast with alternatives like 'send_message'.

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