stape_get_container_logs

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

No annotations exist, so description must fully convey behavioral traits. It does not state whether the tool is read-only, safe, or destructive, nor does it mention rate limits, data retention limits, or output format. This is a significant gap for a data-fetching tool.

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 description is a single, efficient sentence containing the core purpose. No wasted words.

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 and no annotations, the description should at least hint at the response structure or any limits. It does not. The tool's complexity is low, but missing output details makes it hard for an agent to rely on 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 coverage is 100%, and both parameters have clear descriptions (e.g., 'Number of past days to retrieve stats for'). The description adds no additional semantic value beyond what the schema already provides, earning a baseline 3.

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?

Description clearly states the tool retrieves logs, bandwidth, and traffic stats for a container. While specific, it does not differentiate from sibling tools like stape_get_container (which likely retrieves container settings), so a 4 is appropriate.

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 guidance on when to use this tool versus alternatives (e.g., stape_get_container). No exclusions or context about prerequisites or typical use cases provided.

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