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

No annotations are provided, so the description must carry the full burden. It reveals that the tool requires an owner key and retrieves logs from a node, which is useful, but it does not disclose whether the operation is read-only (though implied), whether it can fail if the node is unreachable, or what happens if the specified node isn't running the app.

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 sentences: the first states the action and scope, the second states the requirement. No wasted words, and key information is front-loaded.

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?

Given no output schema, the description could mention return format (e.g., raw log lines) and more behavioral context like error conditions. However, it covers the core operation and key requirement, and parameter descriptions in the schema fill some 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?

The schema has 67% description coverage, and the description adds meaning by clarifying that 'name' refers to the app, 'lines' defaults to fetching the last N lines, and 'component' is for multi-component apps. It also emphasizes the owner key requirement, though it doesn't cover all parameters explicitly.

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?

The description specifies the verb 'fetches,' the resource 'log lines of an app (or one component),' and the scope 'from one of the nodes running it.' This is precise enough to distinguish from siblings like flux_get_app or flux_get_app_stats.

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 implies usage by naming the required owner key and the context (running app on a node), but it provides no explicit when-to-use guidance or alternatives. For example, it doesn't say what to do if the app isn't running or isn't on the expected node.

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