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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that filters apply to a 'persisted log store' and that results are 'recent', but says nothing about truncation, default line counts, or retention limits that would matter when logs come back empty.

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, front-loaded with the action and target, then the filter details. No restated title, no filler; every clause carries 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?

For a 4-parameter read tool with no output schema, most of what an agent needs is present, but the undocumented `lines` parameter and the vague 'recent' window leave real gaps for someone trying to control volume or paginate results.

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?

With schema coverage at only 25%, the description compensates well: it gives concrete accepted formats for `since` (15m, 2h, 3d, or ISO timestamp) and explains that `level` is a token matched inside the log line rather than an enum. The `lines` parameter is left completely unexplained (no default or cap), which keeps it below 5.

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+resource ('Read recent container logs') scoped to a DenkOps project, and the debug-deploy example pins down intent. It doesn't explicitly distinguish itself from nearby observability siblings like get_metrics or get_trace, so it falls short of 5.

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 'e.g. to debug a failing deploy' clause implies when to reach for it, but there are no exclusions or named alternatives (get_trace, get_metrics, list_deployments) for an agent choosing between observability tools. Usage is suggested rather than specified.

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