Register SAP Agent SNS Domain

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

Annotations indicate readOnly=false, destructive=false. Description adds valuable context: it builds/signs/submits transactions, pays fees in USDC+SOL, does NOT set SOL record, and requires separate signature. No contradiction with annotations.

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 concise, front-loaded with key information, and every sentence adds value. No filler or redundancies.

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 tool's complexity (10 params, nested objects, output schema present), the description covers registration process, signer requirements, fee details, and limitations. It is complete and well-paired with the existing annotations and output schema.

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% so baseline is 3. The description does not add detailed parameter semantics beyond the schema, though it provides context about the SOL record being skipped. Overall, adequate but not exceptional.

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 tool registers a .sol domain for the SAP agent wallet using SAP SDK SnsModule, with specific verb 'register' and resource 'domain'. It distinguishes from sibling tools like sap_sns_build_manage_record_transaction by noting that SOL record is not set here.

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?

Explicitly states it's a local-signer-only tool and that hosted accountless SAP MCP rejects it before x402 payment. Provides clear when-not-to-use guidance and directs to use sap_sns_build_manage_record_transaction for setting the SOL record afterwards.

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