Read container logs from a running instance

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the auth requirement (owner key) and that logs are pulled from one of possibly several nodes, but says nothing about whether the call is read-only, side effects, rate limits, or truncation behavior.

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 compact sentences, front-loaded with the core action and scope, with the prerequisite appended. Every clause carries information; nothing is padded.

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 read-style fetch tool with no annotations and no output schema, the description covers the key context an agent needs: what is returned (log lines), the component/node scoping model, and the auth prerequisite. Remaining gaps (default node behavior, line cap) are handled by the schema.

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 only 50%, so the description must compensate. 'Last N log lines' maps to the undocumented `lines` parameter, 'one component of it' maps to `component`, and 'one of the nodes running it' maps to the schema-documented `nodeIp`; only `name` is left implicit. This adds real meaning beyond 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 (fetches) and resource (last N log lines) plus scope (an app, or one component, from one of its nodes). This is clearly distinguishable from siblings like flux_get_app_stats or flux_get_app, which return different resources.

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 description states a prerequisite ('Requires the owner key') but gives no explicit when-to-use/when-not guidance or named alternatives. Usage is implied rather than stated, though the log-fetching purpose is unambiguous enough that no sibling competes for it.

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