Sns Reverse Lookup

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

The description states 'operation class read', implying the tool is a read-only operation. However, the annotation readOnlyHint=false contradicts this, indicating the tool may have side effects or modifications. This contradiction undermines transparency and misleads the agent about the tool's behavior.

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 three sentences long, with the main action in the first sentence. It is concise, front-loaded, and every sentence adds value (action, context, pairing guidance).

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?

The tool has an output schema, so return values need not be described. However, the description does not cover prerequisites, error conditions, or behavioral details beyond the basic purpose. The annotation contradiction also indicates incompleteness. Overall, it is adequate but has clear gaps.

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%, and the description does not add significant meaning beyond the schema. The schema already describes the wallet parameter. Description adds no syntax, format, or example details, resulting in no extra value beyond the baseline.

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 verb ('reverse-lookup'), resource ('.sol domains'), and scope ('owned by a wallet'). It also distinguishes from sibling tools by naming specific pairing tools, making the purpose unambiguous.

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?

The description explicitly defines when to use this tool ('Use to find the SNS domain associated with a wallet') and suggests pairing with sap_sns_resolve_wallet or sap_sns_check_ownership. However, it does not explicitly state when not to use it or provide exclusions.

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