Initiate STC Pay

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

Description lacks behavioral details beyond sending an OTP. No disclosure of side effects, state changes, or prerequisites. The confirmSendOtp guard is only in schema, not described.

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?

Single sentence that is front-loaded with purpose. No extraneous text.

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?

Does not explain prerequisites (must have saved pending checkout), what response looks like, or integration with related tools. Incomplete for an agent unfamiliar with the flow.

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 has 100% coverage with detailed parameter descriptions including mobile normalization. Description adds minimal value beyond schema context.

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?

Description clearly states the verb 'initiate', resource 'STC Pay', context 'saved pending checkout', and outcome 'sends a fresh STC Pay OTP'. Distinguishes from sibling tools like ninja_submit_stc_otp.

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?

Implies usage for initiating STC Pay after checkout creation, but does not explicitly state prerequisites, when to use vs alternatives, or that it must be followed by submit_stc_otp.

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