Generate taxpayer OTP

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

With no annotations present, the description carries the disclosure burden. It reveals the side effect (sending an OTP), the destination (registered mobile/email), configuration fallback behavior (GST_USERNAME/GST_GSTIN), and an external prerequisite (API access enabled). It stops short of mentioning expiry, rate limits, or return shape, 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 three sentences are tight, front-loaded with the step context, and every sentence contributes: role, action, parameters, and prerequisite. No filler or repetition of the tool name.

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 low-complexity tool with two optional params and no output schema, the description covers the essentials: what happens, where the OTP goes, how defaults are resolved, and a prerequisite. It does not state the response format or explicitly recommend proceeding to taxpayer_verify_otp, but those are not blockers for correct invocation.

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?

Both parameters are already documented in the schema (100% coverage), so the baseline is 3. The description adds value by stating that defaults come from config and can be overridden, which explains where the fallback values originate and when to supply explicit gstin/username values.

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 names a concrete action ('Sends an OTP') and a precise target ('taxpayer's GST-registered mobile/email'), and frames it as 'Step 1 of a taxpayer session.' This clearly separates it from the sibling taxpayer_verify_otp tool, which is the follow-up verification step.

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 states clear usage context: this is the opening step of a taxpayer session, so it should precede verify_otp and other taxpayer tools. It does not explicitly list alternatives or when-not-to-use conditions, but the step ordering provides sufficient guidance.

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