get_logs

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

No annotations are provided, so the description must disclose behavioral traits. It only restates the function's basic action without adding context such as read-only nature, meaning of 'recent', pagination/limits, authentication needs, or error behavior. This is a significant gap given the absence of annotation support.

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 fluff, front-loaded with the verb and resource. It is appropriately sized for a simple tool, though it could have added a bit more context without becoming verbose.

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 tool with one optional, fully-documented parameter and an existing output schema, the description covers most needed context. The main omission is defining 'recent' (e.g., lines or time window) and clarifying that the tool returns logs from any of the listed services rather than only 'frigate'. Nevertheless, the schema fills in service details, and the output schema handles return values.

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 schema already fully describes the only parameter, 'service', including allowed values and a default. The description adds no extra semantic meaning beyond the schema, so it meets the baseline for high coverage but does not exceed it.

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 clearly states the verb 'Get' with a specific resource ('recent log output') and scope ('from a Frigate service'). This distinguishes it from all sibling tools, none of which focus on logs, so the purpose is unambiguous.

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?

Usage context is implied: it retrieves recent logs from a service. However, there is no explicit guidance on when to use this tool versus alternatives, no exclusions, and no reference to related log or diagnostic tools. The intended use case (e.g., debugging) is not stated.

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