moose_tail_log

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

No annotations are provided, so the description carries the transparency burden. It discloses the stateful behavior (advancing from_line), the return of newFromLine, and the reset-to-0 handling of truncation/rotation. This goes beyond the schema and provides useful context about how the tool behaves over repeated calls.

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 and front-loaded: 'Tail mode for dcs.log' immediately conveys purpose. Each of the three sentences contributes distinct value: purpose, usage pattern, and robustness. No fluff or unnecessary repetition.

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?

Although there is no output schema, the description mentions 'newFromLine' and 'only new events,' which gives a sense of the return value and behavior. For a simple two-parameter tool with full schema coverage, this is nearly complete, though it could explicitly state the full return structure or error conditions.

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 provides 100% coverage of both parameters, including the meaning of from_line and the instruction to use newFromLine from a previous call. The description reinforces this but does not add substantially new parameter details, so the schema does the heavy lifting.

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 identifies the tool as 'Tail mode for dcs.log' and explains it parses only lines after a given line index for near-live following. This clearly distinguishes it from the full-parse sibling moose_parse_log by focusing on incremental tailing.

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 explicit usage instructions: call repeatedly and advance from_line from the returned newFromLine to get only new events. It also explains truncation/rotation handling. However, it does not explicitly name alternatives or state when not to use it, but the tail semantics make the use case clear.

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