list_log_files

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description contributes the meaningful behavioral fact that omitting `taskmanager_id` broadens scope from one TaskManager to the JobManager, but says nothing about volume, ordering of the returned file list, or any access requirements.

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?

A single sentence that front-loads the default behavior and qualifies it in a trailing clause. Nothing is wasted and nothing needs reordering.

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 an output schema and a full set of annotations, the description needn't cover return values or safety, and it correctly stays short. However, for a two-parameter tool with zero schema coverage, leaving `cluster` entirely unexplained and offering no contrast with `get_logs` leaves real gaps for an agent deciding how to call it.

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 description coverage is 0%, so the description must carry the parameters. It explains `taskmanager_id` well (its effect on scope and where ids come from) but never mentions the `cluster` parameter at all, so half the inputs remain undocumented in both schema and description.

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 ('Log files of the JobManager') and scopes it conditionally: JobManager logs by default, a single TaskManager's logs when `taskmanager_id` is supplied. That is enough to distinguish it from most siblings, though it never contrasts itself with `get_logs`, which is the closest-sounding alternative.

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 conditional ('when `taskmanager_id` is given') is useful in-scope guidance, and it points to `taskmanagers` as the source of valid ids. But there is no explicit statement of when to choose this over `get_logs` or why one would list rather than fetch log content, leaving the main routing decision to inference.

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