sap_sns_get_domain_records

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

No annotations provided, so description carries full burden. It states it fetches records but does not disclose whether it is read-only, idempotent, requires authentication, or has side effects. For a read operation, explicitly stating it does not modify state would improve transparency.

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 with two clauses, no wasted words. Efficiently conveys purpose and output format.

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 simplicity (one parameter, read-only fetch), the description covers the basics. However, it does not mention error scenarios (e.g., non-existent domain) or what the key-value map contains, and lacks annotation-like information such as rate limits or prerequisites.

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 schema description for 'domain' is clear. The description adds no additional meaning beyond the schema (just repeats 'fetch all configured SNS records'), so baseline score of 3 is appropriate.

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 it fetches all configured SNS records for a .sol domain using the Bonfida SDK and returns a key-value map. This distinguishes it from sibling tools like sap_sns_get_record (fetches a single record) and sap_sns_resolve_domain (resolves domain to wallet address).

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. While implied by the name and context (e.g., use for all records vs. specific record), it lacks direct comparison or exclusion statements.

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