Send SMS

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

Annotations already disclose this as a non-read-only, non-destructive, open-world operation. The description adds minimal context by mentioning 'via Kudosity' and 'single recipient', but does not discuss charges, delivery behavior, or failure outcomes, which are useful for a side-effect operation.

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, front-loaded sentence that directly states the action and scope. Every word is meaningful with no unnecessary filler.

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?

While request parameters are fully documented and annotations cover safety, the absence of an output schema means the description should clarify return values (e.g., message ID) or prerequisites like account balance. It does not, leaving a moderate gap for an agent.

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?

Input schema covers 100% of parameters with descriptions, so the baseline is 3. The tool description itself adds no additional parameter meaning beyond the schema, but also does not need to since the schema is thorough.

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 states a specific action ('Send an SMS text message') with a clear resource target ('single recipient via Kudosity'), effectively distinguishing it from sibling tools like send_mms and send_whatsapp by specifying SMS and single-recipient scope.

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 clearly implies use when an SMS needs to be sent to one recipient, but does not explicitly provide exclusions or mention alternatives (e.g., 'for multimedia use send_mms'). It gives a clear context without going further.

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