list_system_logs

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about read-only nature, log volume, pagination, time-range behavior, or retention. Only the word "List" weakly implies a read operation; beyond that the agent learns nothing about how the call behaves.

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?

Three words with zero waste and the action is front-loaded, but the brevity comes from under-specification rather than efficiency. There is no second sentence, so nothing further had to earn its place.

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 no annotations, no output schema, and a no-argument signature, the description is the only source of information an agent has, and it says nothing about scope, ordering, or return shape. It is inadequate for even a simple list tool that sits among a dozen log-related siblings.

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 tool takes zero parameters, so there is nothing for the description to clarify about inputs. Baseline 4 applies per the zero-parameter rule.

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?

"List system logs" restates the tool name verbatim with no added specificity about which logs, what system scope, or what the listing contains. It is a tautology rather than a distinguishing purpose statement, especially against siblings like list_operation_logs and get_container_logs.

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?

No indication of when to use this tool versus the many other log/listing tools in the sibling set (list_operation_logs, get_task_logs, get_ftp_logs, get_host_ssh_logs, get_container_logs). The agent gets no routing guidance whatsoever.

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