sap_sns_resolve_domain

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

With no annotations, the description lists the types of data returned (identity, wallet, metadata, records) but does not disclose whether the operation is read-only, idempotent, requires permissions, or has side effects. The transparency is adequate but incomplete for a mutation-ambiguous context.

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?

A single sentence of 20 words efficiently conveys the purpose and outputs. It is front-loaded with the verb 'Resolve' and contains no filler. Every word earns its place.

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?

While the description lists key outputs, it lacks specification on whether the 'domain' parameter is required (schema shows 0 required) and does not provide usage context relative to similar sibling tools. For a simple tool, it is minimally adequate but could be more complete.

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?

The schema description already covers the 'domain' parameter well (100% coverage). The tool description adds extra detail by mentioning 'wallet' and 'metadata' as outputs beyond 'identity and SNS records', enhancing understanding beyond the schema.

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 action 'resolve', the resource '.sol domain', and the outputs: 'SAP agent identity, wallet, metadata, and SNS records'. It distinguishes from similar siblings like 'sns_resolveDomain' by specifying the SAP SDK SnsModule, making the tool's unique role clear.

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 guidance is provided on when to use this tool versus alternatives like 'sns_resolveDomain' or 'sap_sns_check_domain'. There are no prerequisites, usage conditions, or exclusions mentioned.

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