tail_log_live

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

No annotations exist, so the description carries full burden. It discloses the polling behavior for streaming, which is important. However, it lacks details on rate limits, authentication, or what happens on incomplete polls, and there is a minor inconsistency between 'next_byte' (mentioned) and the actual parameter 'start_byte'.

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 sentence of 13 words, front-loaded with the purpose, and contains no filler. Every word earns its place.

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?

Despite having 4 parameters and no output schema, the description does not explain the return format or how 'next_byte' is provided in responses. For a streaming/polling tool, this leaves a significant gap in completeness.

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 coverage is 100%, so each parameter is already documented. The description adds context about repeated polling with 'next_byte' which relates to start_byte and max_bytes, but does not provide new semantic meaning beyond the schema.

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 a specific verb ('Get') and resource ('log chunk') and clearly states the purpose is for live tailing by polling repeatedly. It distinguishes itself from siblings like get_build_log (full log) and search_log (search) via the streaming implication.

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 explicitly mentions the polling pattern with multiple calls and the 'next_byte' concept, giving clear usage context. However, it does not provide explicit when-not-to-use guidance or alternative tools, though the streaming hint differentiates it from one-shot log fetches.

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