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

With no annotations, the description carries the full burden and does so well: it discloses the validate→quote→sign→broadcast→pay pipeline, that signing uses the Flux ID, that payment comes from the payment address, and that confirm=false is non-spending. It stops short of stating that confirm=true spends real funds irreversibly or whether payments are refundable.

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 tight sentences, front-loaded with the core action and the confirm gate, with no redundant text; every clause adds decision-relevant information.

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 complex, nested, payment-executing mutation with no annotations and no output schema, the description covers the operation flow, the spend/no-spend distinction, and the follow-up call. It could be more explicit about irreversibility and required funding of the payment key, but is nearly complete.

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 already 80%, so the schema documents confirm, the key parameters, and spec fields. The description reinforces the confirm semantics and the payment-source concept but adds little syntax or format detail beyond what the schema provides, so baseline 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?

States specific verbs and resource: validates, quotes, signs, broadcasts, and pays for an app; and explicitly disambiguates the confirm=true vs confirm=false behavior. It also clarifies that it registers a new name or updates an existing app of the same owner.

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?

Clearly explains when to use confirm (to actually sign/broadcast/pay) versus when not to (plan-only, spends nothing), and routes to flux_wait_for_app with the returned txid. It does not, however, differentiate from close siblings like flux_quote_app or flux_validate_spec, which an agent might otherwise pick for pricing or validation.

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