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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds real value on top by clarifying that no money moves at creation time, that buyer contact only happens when send_email/send_sms are true, and that the endpoint is POST /payment-requests/. It omits auth requirements and rate limits.

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?

Four tight sentences, front-loaded with the "WRITE:" marker and the primary outcome, then money semantics, then notification caveats, then the endpoint. No filler sentences.

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?

With 10 parameters and no output schema, the description compensates by naming the return fields (id, longurl, shorturl) and the unit of amount. Only the broader response payload shape and error behavior are left unmentioned, which is acceptable.

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 description coverage is 100%, so every parameter (including the email/phone-conditional and webhook/redirect semantics) is already documented in the schema. The description's notes on INR and the email/phone prerequisites largely restate schema content, so it sits at the baseline rather than adding new meaning.

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?

States a specific verb and resource ("create a payment request (a payment link)") plus the returned artifacts (id, longurl, shorturl), which cleanly separates it from siblings like instamojo_get_payment_request, instamojo_list_payment_requests and the enable/disable pair.

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?

Explains the transactional model — nothing is charged and the buyer pays on the link — plus the conditional notification behavior, which tells the agent when this tool versus a charge/refund flow applies. It does not explicitly name a sibling to prefer or state exclusions, so it stops short of full routing guidance.

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