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

Annotations already declare readOnlyHint and openWorldHint, and the description adds the owner-key auth requirement plus the single-node scoping. It does not say whether stats are sampled live or cached, what granularity/window they cover, or any rate limit, leaving meaningful behavioral gaps for a monitoring call.

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 tight sentences with the resource front-loaded and the auth requirement trailing; nothing is wasted. It is efficient, though bordering on under-specified rather than richly concise.

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?

With readOnly/openWorld annotations and no output schema, the safety profile is covered, but the description does not say what the returned stats contain (per-container? aggregates? units?) or how node/component interact, which an agent needs to interpret results for a 5-parameter tool.

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 the schema documents the two private keys itself. The description contributes 'on one node' (implying nodeIp) and 'owner key' (implying fluxIdPrivateKey), but says nothing about 'component' for multi-component apps or how nodeIp defaults when omitted.

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: live CPU, memory and network stats for the containers of an app on one node. This is distinguishable from flux_get_app (metadata) and flux_get_app_logs (logs) by the 'stats' resource, though no sibling is named 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?

There is no explicit when-to-use, no condition selecting this over flux_get_app or flux_get_app_logs, and no exclusion. 'Requires the owner key' is an auth prerequisite rather than usage guidance, so the agent must infer the monitoring/metering context.

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