androidapi_send_otp

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

The description explains the placeholder mechanism and the delivery channels, but does not disclose other behaviors like OTP generation, error handling, or specific requirements per mode. Annotations indicate readOnlyHint=false which matches the write nature.

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?

Two concise sentences that front-load the main purpose and essential detail about the placeholder. No superfluous words.

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 complexity of 10 parameters with conditional logic, the description lacks coverage of trade-offs between modes, required IDs, and OTP expiry. No output schema compensates.

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 coverage is 100% with detailed parameter descriptions. The description adds context about the {{otp}} placeholder but does not significantly enhance understanding beyond the schema.

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 verb 'Send' and the resource 'OTP to a phone number via SMS or WhatsApp', and mentions the specific placeholder mechanism. It differentiates from sibling tools that send general messages.

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?

No explicit guidance on when to use this tool versus alternatives like androidapi_send_sms or androidapi_send_whatsapp. Prerequisites such as device or gateway setup are not mentioned.

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