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

With no annotations, the description carries the full burden; it does disclose a genuine auth precondition ('Requires the owner key'), which is useful. However it omits whether the call is read-only, whether the app must be actively running, latency/rate characteristics, or what the response contains.

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?

Two short sentences, no filler, with the core resource and the precondition front-loaded and immediately scannable.

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 5-parameter, no-output-schema, no-annotation tool, the description is thin: it never clarifies optional params (nodeIp, component), key selection, or what happens when the app is not running. It is minimally adequate but leaves real gaps.

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 60%, so several parameters are undocumented there; the description hints at 'one node' (nodeIp) and 'containers of an app' (component) but never maps them explicitly, and it says nothing about the two private-key parameters or which key 'owner key' corresponds to.

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 ('CPU, memory and network stats of the containers of an app') plus scope ('on one node'). This clearly distinguishes it from siblings like flux_get_app (config) and flux_get_app_logs (log output).

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 only contextual hint is 'Requires the owner key', which is a precondition rather than usage guidance. Nothing tells the agent when to prefer this over flux_get_app_logs, flux_get_app, or flux_wait_for_app, or whether the instance must be running.

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