K8S Logs

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

No annotations are provided, so the description must disclose behavior, but it only gives a noun phrase and a CLI command hint. It does not mention whether logs are fetched once or streamed, what namespace/pod context is needed, or any other operational 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?

The phrase is short, but this is under-specification rather than effective conciseness. Like the 'process' example, it is too minimal to convey how the tool should be used and does not earn its place because it conveys almost no actionable information.

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?

Both the schema and description are nearly empty, and the sibling list contains many competing log-related tools. An agent has no way to know how to invoke this correctly, even with an output schema present, because the required inputs are completely undescribed.

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 input schema has a single opaque 'params' object with additionalProperties true and 0% schema description coverage. The description does not specify expected keys such as pod name, namespace, or container, so it completely fails to compensate for the undocumented parameter.

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 'Логи пода (kubectl logs)' is a noun phrase that restates the tool name 'K8S Logs' and adds only a parenthetical kubectl hint. It does not describe an action like 'retrieve' or 'stream', and it does not differentiate this tool from siblings such as k8s_events or k8s_describe.

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 guidance about when to use this tool instead of alternatives like k8s_describe, log_tail, or service_logs. No context or exclusion criteria are provided, leaving the agent to guess which of the many log-related tools is appropriate.

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