build_update_creator_profile_transaction

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

There are no annotations, so the description must carry the behavioral burden. It discloses the BAOZI_LIVE=1 requirement and implies that the tool only builds (not submits) a transaction. But it does not disclose wallet authorization, return value, or what happens if the creator does not exist, leaving some ambiguity for an agent.

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?

Two short sentences, front-loaded with the key purpose and prerequisite. The second sentence largely duplicates schema requirements, but it is compact and does not waste 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?

For a simple three-parameter transaction builder with no output schema, the description states purpose, prerequisite, and required fields. However, it does not explain the return value or how it relates to transaction submission/execution, which an agent would need to invoke it correctly in a broader workflow.

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 already documents all three params with constraints (max 32 chars, max 50 bps). The description adds only a repeat that display_name and default_fee_bps are required, omitting creator_wallet from that statement; this adds no semantic value 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?

The description states a specific action ('Build transaction to update creator profile') with a clear resource ('creator profile') and verb ('update'), distinguishing it from sibling build_create_creator_profile_transaction. The 'REQUIRES BAOZI_LIVE=1' prefix adds an environmental precondition but doesn't obscure purpose.

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 gives an implied use case (updating creator profiles) and a clear prerequisite (BAOZI_LIVE=1), and repeats that both display_name and default_fee_bps are required. However, it does not explicitly contrast with sibling build_create_creator_profile_transaction or explain when not to use it, so guidance is only implied.

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