sap_sns_build_manage_record_transaction

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

With no annotations, the description carries the burden. It discloses the unsigned nature, the need for separate signing, the null-for-delete mechanism, and the SOL exclusion. It does not mention potential fees or error cases, but for a transaction builder this is thorough.

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?

Three short sentences, front-loaded with the core purpose. Every sentence adds essential information: what it does, what to do with the result, and a key exception. No wasted words.

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 no output schema, the description covers the workflow adequately: build, sign, submit (implied). It addresses the SOL record limitation and null usage. It could optionally mention that the transaction includes instructions for the record type, but is sufficiently complete for a builder tool.

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%, so baseline is 3. The description adds value by clarifying that null deletes, that owner is the authorizing key, and that the returned transaction needs signing. It also gives examples of record types, but that is already in 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?

The description clearly states it builds an unsigned transaction for creating, updating, or deleting SNS records using the Bonfida SDK. It distinguishes from sibling query tools like `sap_sns_get_record` and mentions the unsupported SOL record, which further clarifies scope.

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?

It provides explicit guidance: use for CRUD on SNS records, must be signed with `sap_sign_transaction` before submission, use null to delete, and that SOL record requires a different flow. This covers when, how, and when-not to use.

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