modal_container_logs

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Fetch logs,' implying a read operation, but does not disclose output format, default log limits, pagination, or error behavior when the container ID is invalid. This is a significant gap for a tool with no annotations.

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 concise sentence with no filler or redundant information. Every word earns its place, and it is front-loaded with the primary action and resource.

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?

This is a minimal description for a tool with 4 parameters, no output schema, and no annotations. It lacks essential context about return values, how tail/since/source interact, and the relationship to modal_app_logs. The agent would need to rely on the schema alone, which is insufficient for complex usage.

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 100% with descriptions for tail, since, source, and containerId. The description adds no extra parameter meaning beyond what the schema already provides, so the baseline of 3 is appropriate. It does not explain relationships between parameters or provide examples.

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 'Fetch logs for a specific container' clearly states the verb (fetch), resource (logs), and scope (specific container). This distinguishes it from sibling tools like modal_container_list (lists containers) and modal_container_exec (executes commands in a container), while the phrase 'specific container' implies the need for a container ID.

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 on when to use this tool versus alternatives such as modal_app_logs (which fetches app-level logs) or modal_container_list. The description only states what it does, not the context or exclusions, leaving the agent without explicit decision support.

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