Build SNS Manage Record Transaction

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

Discloses beyond annotations: builds unsigned transaction, requires subsequent steps, null value special behavior, SOL record limitation. Annotations already indicate not read-only, not idempotent, not destructive, so description adds useful 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?

Four sentences, front-loaded with the primary action. No redundant information, each sentence adds value.

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?

Covers main operation, post-processing, null deletion, and unsupported SOL record. Could mention the output (unsigned transaction object) but output schema exists to handle that. Adequate for a 4-parameter tool with no required parameters.

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 covers all 4 parameters with descriptions (100% coverage). Description adds little beyond schema: the null value hint is already in schema. The note about SOL record gives domain-specific constraint but not deeply about parameter usage.

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?

Clearly states it builds an unsigned SNS record create/update/delete transaction using Bonfida SDK. Differentiates from sibling tools like sap_sns_get_record or sap_sns_build_set_primary_domain_transaction.

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?

Explains two modes (hosted vs local) and how to chain with sap_payments_finalize_transaction or sap_sign_transaction. Also mentions using null to delete and that SOL record is not supported. Lacks explicit alternatives for unsupported operations but is clear in context.

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