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

With no annotations, the description carries the full burden and does well: it discloses the term-rewrite mechanism, that the network uninstalls everywhere, that confirm=true signs and pays a minimal fee, and that omitting confirm returns the plan (a dry run). It does not state irreversibility of the uninstall or required ownership permissions beyond what the schema's key params imply.

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 short sentences, front-loaded with the core action and mechanism, then the payment/confirm behavior. No filler; every sentence carries 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 mutation tool with no annotations and no output schema, the description covers side effects, cost, and the dry-run return. It could be stronger on permissions, reversibility, and what the returned plan contains, but it is largely sufficient to call correctly.

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% (name undocumented, private keys documented in schema), and the description meaningfully covers the undocumented confirm parameter by explaining both branches: signing/paying versus returning the plan. It adds real semantic value over the bare boolean default.

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 and resource ('Ends an app early by updating its term so it expires within about an hour') and clarifies the novel mechanism rather than just saying 'cancel'. It is distinguishable from siblings like flux_control_app and flux_deploy_app, though it never names an alternative 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?

Usage is implied by the action ('end an app early'), and the confirm flag's two modes are explained, but there is no explicit when-to-use vs when-not or pointer to a sibling tool for related operations.

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