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

With no annotations, the description carries the full burden and does disclose meaningful traits: bounded polling duration, idempotent repeat-safety until done=true, and the set of results returned. It omits any note on permissions or what happens on a timeout hit (does it throw, return partial state, or leave the app pending), which is the one real gap.

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 dense sentences, all front-loaded: what it does, the timeout constraint and its rationale, then the return payload and idempotency note. No filler and nothing repeated from the schema.

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?

No output schema exists, so the description correctly spells out the return shape (confirmations, acceptance, instances with URLs). Combined with the timeout rationale it covers most of what a 6-param polling tool needs, though timeout-expiry behavior is unstated.

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 67%, and the description adds real meaning beyond it for timeoutSeconds: the default 45 exists to fit a 60 s host tool timeout and the max is 600. It also flags that payment confirmations require a txid, tying the txid param to an outcome. txid/previousHash/private-key params are left to 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?

States a specific verb+resource: polls the network for deployment acceptance and running instances, naming the returned artifacts (payment confirmations, spec acceptance, instances with URLs). It is distinguishable from siblings like flux_deploy_app and flux_get_app, though it never names them explicitly.

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 closing sentence 'Safe to call repeatedly until done=true' gives polling guidance, and the timeout rationale hints at when 45s is appropriate. But it never states when to prefer this over flux_get_app or when the wait is unnecessary, leaving the alternative choice implicit.

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