jio_send_otp

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

With no annotations provided, the description takes on full behavioral disclosure. It reveals the side effect (sending an SMS) and precondition (first login, no local session), which goes beyond a simple action phrase. It does not cover edge cases like rate limits or OTP expiration, but the core behavior is transparent.

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, efficiently structured sentence that front-loads the verb and resource, then adds the usage condition in parentheses. No words are wasted.

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?

For a simple 0-parameter tool with no output schema, the description provides sufficient context: what it does, when it is needed, and its place in the login flow. It could explicitly mention the next step (e.g., jio_verify_otp), but this is implied by the login sequence.

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 tool has zero parameters, so there is nothing to explain beyond the schema. The description mentions 'JIOAICLOUD_MOBILE' as a fixed destination, not a parameter, which adds clarity without needing parameter documentation.

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 login OTP SMS') and the specific destination ('JIOAICLOUD_MOBILE'), making the tool's purpose unambiguous. It also differentiates from sibling tools like jio_verify_otp and jio_login by explaining its role in the login flow.

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 provides explicit when-to-use guidance: 'needed only for first login when no local session exists.' This implies when not to use it (if a local session already exists), though it does not explicitly name alternative tools.

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