Resolve SAP SNS Domain

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds context about the return content (agent identity, wallet, metadata, SNS records) and mentions using 'SAP SDK SnsModule', but does not elaborate on other behavioral aspects like rate limits, authentication needs, or cost.

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, well-structured sentence that front-loads the purpose and lists key outputs. No unnecessary words, making it highly concise for the information it conveys.

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 existence of an output schema, the description provides appropriate high-level context of what is returned. However, it lacks details on edge cases, prerequisites, or comparison to similar SNS tools, which would be beneficial for completeness.

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%, with the parameter 'domain' described in the schema. The description does not add any additional parameter semantics beyond what the schema already provides; it only restates the purpose in broader terms.

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 (resolve) and target (.sol domain), listing specific outputs (SAP agent identity, wallet, metadata, SNS records). This differentiates from the sibling 'sns_resolveDomain' which likely resolves domains generally, but does not explicitly contrast with other SNS tools like 'sap_sns_resolve_wallet'.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it is for resolving .sol domains to SAP-specific data, but does not mention when not to use it or name specific alternatives among the many SNS sibling tools.

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