Enable rebalancing for a vault (initialize_rebalancer)

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

Despite annotations already declaring readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, the description adds substantial context the annotations cannot: it is a gated REAL-MONEY operation, requires manager/admin rights, the creator pays rent, it runs as prepare → sign → submit, and it reverts if the config is already initialized.

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?

Front-loaded with the gating and authorization constraint first, then the effect, then the disambiguation of when it is required. Every clause carries information; nothing is repetitive or padded.

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?

With no output schema, the description still covers the full picture an agent needs: authorization requirement, cost/rent payer, execution flow, revert-on-reinit behavior, and the conditions under which the tool is unnecessary. Nothing material is missing for a correct invocation.

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 50% (vault has only a pattern, confirmPhrase is fully documented in the schema). The description still adds meaningful semantic constraints on the vault argument — it must be one the caller's app wallet ADMINS — which is not expressible in the schema and directly affects a valid call.

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?

States a specific action and resource: it creates the vault's RebalancerConfig so the vault can be rebalanced, distinct from launch_vault (bundles it automatically) and rebalance_to_targets (performs the rebalancing). The agent can tell exactly what this tool produces without opening the schema.

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?

Explicitly scopes when this is needed (older vault, vault created with rebalancing skipped, or basket too large to bundle) and when it is not (vaults launched by this agent already get it bundled at create time). It also states the explicit precondition that the caller's app wallet must ADMIN the vault.

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