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

Annotations flag destructive/non-idempotent/open-world, and the description adds substantial context beyond them: payment is drawn from the payment address, signing uses the Flux ID, and the no-confirm path is a safe dry run that spends nothing. This exposes the two-phase commit and spend behavior an agent must reason about.

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 compact sentences, front-loaded with the confirm/no-confirm decision, then the register-vs-update scope, then the follow-up call. Every sentence carries distinct load.

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 destructive 5-param tool with nested objects and no output schema, the description covers the mutation path, the safe preview path, identity/payment keys, and the returned txid handoff. Nothing essential for correct invocation is missing.

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 high (80%), so the schema already documents spec, confirm, keys, and enterprise. The description reinforces confirm and the payment-address semantics without adding syntax beyond the schema, so it sits just above the baseline for high-coverage schemas.

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 specific verbs and resource: validates, quotes, signs, broadcasts, pays for an app. Explicitly covers both 'register a new name' and 'update an existing app of the same owner', distinguishing it from siblings like flux_validate_spec and flux_quote_app.

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?

Gives the key conditional: with confirm=true it signs/broadcasts/pays, without confirm it only returns the plan and spends nothing. Also names the follow-up tool (flux_wait_for_app) and the txid to pass. This is explicit when-to-use and what-happens-next guidance.

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