build_remove_from_race_whitelist_transaction

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

With no annotations, the description carries the full burden of disclosing side effects and behavior. It indicates the tool builds a transaction but does not clarify whether it submits, signs, or requires specific permissions. The BAOZI_LIVE flag is a prerequisite, not a description of runtime behavior, so the tool's actual effects remain opaque.

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 a single concise sentence that immediately communicates the core purpose and includes a critical requirement. No filler words or redundant information; it is well-structured and front-loaded.

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 transaction builder with no output schema and no annotations, the description lacks essential details about return values, transaction structure, or any side effects. It does not explain what the agent can expect from the tool or how it fits into the broader transaction workflow, making it incomplete for reliable usage.

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 description coverage is 100% and each parameter has a clear description (e.g., 'Race market public key'). The tool description adds no additional parameter meaning beyond the schema, so the baseline of 3 applies.

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 action: 'Build transaction to remove user from race whitelist.' It uses a specific verb and resource, and the 'race' qualifier distinguishes it from the non-race whitelist sibling (build_remove_from_whitelist_transaction) and the add counterpart (build_add_to_race_whitelist_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?

The description only mentions a prerequisite flag ([REQUIRES BAOZI_LIVE=1]) but gives no guidance on when to choose this tool over alternatives like build_remove_from_whitelist_transaction. There is no explicit context or exclusions provided, leaving the agent to infer usage solely from the tool name.

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