services_logs

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

With no annotations present, the description carries the full burden of conveying behavior. It signals a read-only operation via "Read" and reveals pagination behavior through "cursor from a previous response," which adds useful context. However, it does not explain how pagination is initiated, whether output is truncated, or any access/permission expectations.

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 compact: one clear purpose sentence followed by a terse args block. Every line adds some information, and there is no filler or redundancy with the schema.

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 an output schema exists, the lack of return-value documentation is acceptable. However, the description does not state how to obtain a cursor initially, how log levels are formatted, or how to discover valid service names, which an agent may need for correct invocation. It is minimally adequate but not fully self-contained.

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 has 0% property description coverage, so the description must compensate. It gives brief but understandable meanings for all four parameters, especially "cursor: Pagination cursor from a previous response" and "level: Optional log level filter." Still, it leaves details open, such as accepted log level values and any limits on the limit 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 opens with "Read a service log," a specific verb plus resource, and the required service parameter clearly identifies which log is being read. It does not explicitly contrast with siblings like services_get or services_list, but the log-reading 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?

There is no guidance about when to use this tool versus alternatives such as services_get, services_list, or other diagnostic tools. The description does not mention prerequisites, such as knowing valid service names, nor when reading logs would be preferable to checking service status.

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