Tail logs

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

The description adds behavioral context beyond the readOnlyHint annotation by stating the operation is 'finite' (not streaming) and can 'scan older pages' (indicating pagination/backward traversal). It does not describe return format or rate limits, but given the annotation, this is acceptable.

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, focused sentence with no unnecessary words, front-loading the core action and optional behavior.

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?

The tool has 15 parameters and no parameter descriptions or output schema; the description doesn't clarify which identifiers are required, how scanning works, or what the return structure is. This leaves significant gaps for an agent trying to invoke it correctly.

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 only explains 'level' and 'since' filters and perhaps 'limit' implicitly via 'finite' page. The other 12+ parameters (identifiers like project_id, run_id, deployment_id, approval_token) are left unexplained, so agents must guess their meaning.

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 uses specific verbs 'Fetch' and 'scan' with a clear resource ('deployment log page'), and distinguishes itself from siblings like follow_logs by emphasizing 'finite recent' and optional scanning of older pages.

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?

It provides clear context: fetching a finite recent page and optionally scanning older pages with level/since filters, implying a snapshot-style read. However, it does not explicitly name alternatives or when-not-to-use cases, leaving some ambiguity among log-related siblings.

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