get_logs

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

The description discloses that the tool reads buffered non-error logs with cursor-based pagination. However, with no annotations, it fails to cover authorization, rate limits, or behavior when the buffer is empty, leaving notable gaps.

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 front-loaded with the action and resource. However, it could include more detail 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?

Given six parameters, no annotations, and no output schema, the description is insufficient. It omits parameter explanations, return format, and usage context, making it incomplete for effective tool selection.

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 0% schema description coverage, the description adds minimal parameter context, only hinting at `sinceCursor` and `limit` via 'cursor-based pagination.' It does not explain `sessionId`, `levels`, `tags`, or `sources`, leaving agents to infer meaning from names alone.

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 specifies 'Read buffered non-error logs using cursor-based pagination,' clearly stating the verb 'read' and resource 'non-error logs.' This distinguishes it from the sibling `get_errors`, which targets error logs.

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 description implies usage for reading non-error logs with pagination but offers no explicit guidance on when to use this tool versus alternatives like `get_errors` or when not to use it.

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